Low-Power WUS Rel-19

RAN1#116

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-234056 for detailed scope of the WI.

[116-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2400640 Work plan for Low-power wake-up signal and receiver for NR vivo, NTT DOCOMO

9.6.1 LP-WUS and LP-SS design

R1-2400123 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

Both OOK1 and OOK4 with overlaid sequence(s) are supported, where OOK-1 is specified as a special case of OOK-4 with M=1.

Only the same SCS between LP-WUS and legacy NR signals that UE MR processes is supported.

Support the following design

· All the bits carried by one LP-WUS are divided as bit block 1 and bit block 2,

o Bit block 1 is carried by/modulates the ON/OFF pattern of the first M OFDM symbols

o Bit block 2 is carried by/modulates the overlaid sequences in the first M OFDM symbols.

§ According to bit block 2, one overlaid OFDM sequence selected from a set of candidate OFDM sequences is on each OOK ON symbol

§ Bit block 2 can also modulate the ON/OFF pattern of the remaining N-M OFDM symbols.

· One LP-WUS consists of N OFDM symbols

Further discuss and adopt sequence(s) considering the following aspects:

· Sequence with good auto-correlation property and cross-correlation property

· How to control the interference from LP-WUS transmitted from neighboring cells

ZC sequences are considered as a starting point for the design of overlaid sequence(s).

Pulse shape and/or spectrum shape are also considered in the design/selection of overlaid sequence(s).

Support overlaid sequence(s) with a number of zero value samples at the beginning and the end of the sequence to have a concentrated waveform for time domain pulse shaping of LP-WUS.

The value of ACS/ASCS should be further converged in WI phase in RAN4, which may have impact on LP-WUS/LP-SS design in RAN1.

Time domain repetition and transmit diversity by precoder cycling are considered to improve the performance of LP-WUS.

Coverage recovery schemes that exploits time / frequency diversities are considered.

Binary spreading sequences are considered to multiplex WUSs on the same time-frequency resource and to improve the BLER.

As the starting point, the waveform of LP-SS can have similar design as LP-WUS, including at least the following aspects：

· pulse shaping methods, including the concentrated waveform and the spectrum adjustment

· overlaid sequence(s)

Consider LP-SS specific design requirement, including at least larger guard band/subcarrier, and shorter OOK symbol length.

The design of LP-SS should consider the CP impact and the length of binary-valued sequence to generate LP-SS.

For the OOK sequence of LP-SS, consider at least the following design principles

· Binary sequence with good auto-correlation property

· Limited length of consecutive '0's

· '0's and '1's inside the binary sequence are balanced

A set of candidate values for LP-SS periodicity can be defined, which are not larger than 320ms.

For serving cell RRM measurement offloaded from MR to LP-WUR, LP-RSRP and LP-RSRQ are introduced and specified as LP-SS based metrics.

Further discuss whether existing SS-RSRP definition is reused for RRM serving cell measurement by OFDM based LP-WUR or define new LP-RSRP2 and LP-RSRQ2 by using existing SSS for LP-WUR that can receive PSS and SSS.

Decision: The document is noted.

R1-2401146 LP-WUS and LP-SS design Ericsson

· Following principles should be considered for LP-WUS and LP-SS design

o It should be possible to generate LP-WUS/LP-SS transmissions using existing gNB hardware and not trigger any new emissions or compliance requirements.

o It should be possible to multiplex the LP-WUS/LP-SS with other NR transmissions in time or frequency domain without causing interference.

o It should be possible to reuse any unused LP-WUS time and frequency resources for other transmissions.

· Paging misdetection performance of the UE should not be impacted when LP-WUS is used by the UE for power savings.

· Same sub-carrier spacing (SCS) should be used for LP-WUS and other NR transmissions in the same CP-OFDMA symbol.

· SCS used for LP-SS and Idle mode LP-WUS transmission should be same as the SCS used for initial BWP.

· Including a preamble part before the data part of LP-WUS transmissions should be considered.

· Performance of sequence-based and payload-based LP-WUS structures should be studied further.

· WUS payload size should be at most 8 bits in Idle/Inactive. Similar payload size should be considered for Connected mode.

· OOK-1 should be supported for LP-WUS. If OOK-4 is also supported, it should be with small M (e.g., M ≤ 4).

· LP-WUS design should allow OFDM-based LP-WUR to detect the information sent using OFDM sequences using a smaller monitoring duration compared to that of OOK-based LP-WUR (which detects information sent via OOK).

· It should be possible for NW to flexibly configure the placement of LP-SS resources in frequency and time to minimize overhead and NW energy efficiency impact.

· Consider following values for configuring LP-SS periodicity: 320ms, 640ms, 1280ms, 2560ms, 5120ms, 10240ms (higher values preferred).

Decision: The document is noted.

R1-2400065 Discussion on LP-WUS and LP-SS design Spreadtrum Communications

R1-2400093 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2400211 Discussion on LP-WUS and LP-SS design Transsion Holdings

R1-2400253 Discussion on LP-WUS and LP-SS design vivo

R1-2400272 Discussion on LP-WUS and LP-SS Design TCL

R1-2400338 Discussion on LP-WUS and LP-SS design CMCC

R1-2400444 Design of LP-WUS and LP-SS CATT

R1-2400473 Discussion on LP-WUS and LP-SS design NEC

R1-2400495 Discussion on LP-WUS design ZTE, Sanechips

R1-2400527 Discussion on LP-WUS and LP-SS design Honor

R1-2400569 Discussion on LP-WUS and LP-SS design xiaomi

R1-2400590 Signal design for LP-WUS and LP-SS OPPO

R1-2400634 Discussion on LP-WUS and LP-SS design Sharp

R1-2400670 Discussion on LP-WUS/LPSS design China Telecom

R1-2400684 Discussion on LP-WUS and LP-SS design framework for Low power WUS InterDigital, Inc.

R1-2400743 LP-WUS and LP-SS design Samsung

R1-2400811 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2400813 Discussion on LP-WUS and LP-SS design Everactive

R1-2400863 LP-WUS and LP-SS design Sony

R1-2400883 Discussion on LP-WUS and LP-SS design Lenovo

R1-2400904 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2400962 LP-WUS and LP-SS design Nokia, Nokia Shanghai Bell

R1-2401023 LP-WUS and LP-SS design Apple

R1-2401126 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2401150 Views on LP-WUS and LP-SS design KT Corp.

R1-2401208 Discussion on LP-WUS and LP-SS design Fujitsu

R1-2401317 On LP-WUS and LP-SS design MediaTek Inc.

R1-2401335 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2401349 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2401452 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2401665 Summary of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement:

Support both OOK-1 and OOK-4 for LP-WUS.

· FFS how OOK-1 and OOK-4 are specified

· For OOK-4, M<=4, FFS supported values

· The SCS of a CP-OFDM symbol used for LP-WUS generation can be the same as one of the SCS(s) used for other NR transmissions in the same CP-OFDM symbol

o FFS different SCS.

Agreement:

Further study the following options for LP-SS:

· Option 1: OOK-1

· Option 2: OOK-4 with M=1,2,4,[8]

· The SCS of a CP-OFDM symbol used for LP-SS generation is the same as that used for LP-WUS generation

o FFS: different SCS

R1-2401746 Summary#2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday session

Agreement

For LP-SS design from RAN1 perspective, consider at least the following as the design target:

For RRM measurement performed by LP-WUR based on LP-SS, UE can satisfy measurement accuracy based on X LP-SS samples within a period which is comparable to Y=the length of I-DRX cycle that is larger or equal to 1.28s.

FFS: X
Note: Y is chosen for evaluating LP-SS design.
Network overhead and network power consumption are to be considered.

Agreement

The ‘ON-OFF’ pattern for OOK symbols of LP-SS is based on binary sequence(s)

· FFS binary sequence(s) details, including the sequence type, the number of sequences, and the sequence length.

· FFS overlaid OFDM sequences, if supported.

Agreement

For the overlaid OFDM sequence(s) for LP-SS, consider the following options for further down-selection:

· Option 1: Do not specify the overlaid OFDM sequences(s)

· Option 2: Specify the overlaid OFDM sequence(s) targeting for OOK waveform generation without targeting for sync and RRM measurement for OFDM-based LP-WUR using the overlaid sequence of LP-SS.

· Option 3: Specify the overlaid OFDM sequence(s) targeting for OOK waveform generation and also targeting for sync and RRM measurement for OFDM-based LP-WUR using the overlaid sequence of LP-SS.

· For Option 3, it is up to RAN4 to make decision on whether/how to define the RRM measurement requirement for OFDM-based LP-WUR using the overlaid sequence of LP-SS.

R1-2401837 Summary#3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Agreement

For RAN1 evaluation purpose, the SNR to achieve the coverage of PUSCH for message3 is determined for OOK-based LP-WUR and OFDM-based LP-WUR, respectively.

· Companies are encouraged to report the SNR, together with the associated assumptions as listed in the table below.

Bandwidth for LP-WUS signal (MHz)

NF for LP-WUR (dB)

Gain of antenna element (dBi) assumed for LP-WUR:

e.g., -3 dBi for redcap UE and e.g., 0dBi for non-redcap UE

# of Tx chains for LP-WUS/LP-SS transmission, e.g., 2

Note: The number of Tx chains for LP-WUS/LP-SS transmission is assumed the same as the number of RX chains for MSG3 reception

MIL value of MSG3: taking redcap UE /non-redcap UE @dense urban 2.6GHz

The SNR (dB) to achieve the coverage of PUSCH for message3

Companyname-01

Final summary in R1-2401863.

For information

R1-2401871 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2401024 LP-WUS operation in IDLE/INACTIVE modes Apple

At least the following configuration information for LP-WUS is broadcast in a SIB message:

· Offset of LP-WUS monitoring occasion relative to PO

· Subgrouping related information (e.g. the total number of subgroups, and the number of UE ID based subgroups)

Consider the following options for multi-beam support of LP-WUS monitoring:

· Option 1: the monitoring occasion for each beam is individually defined.

· Option 2: a monitoring time window is defined to cover all the beams.

The activation and deactivation of LP-WUS monitoring by LP-WUR is left to UE implementation.

It is up to UE implementation whether to monitor paging DCI or PEI (if configured) after receiving LP-WUS (no specification impact).

MR waking up from deep sleep state, in addition to ultra-deep sleep state, is supported, via supporting smaller value(s) for the offset between LP-WUS monitoring and PO.

Decision: The document is noted.

R1-2401318 On LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

At least ramp-up time of 400 ms and 800 ms for MR are supported for Rel-19 LP-WUS.

Table 1: Power model for Main Radio (quoted from Section 6.3.1 of TR 38.869)

Power State

Relative Power (unit)

Ramp-up and down transition energy (Note1):

(unit multiplied by ms)

Ramp-up time

Time for sync/re-sync

Appendix A Ultra-deep sleep

Appendix B 0.015

Appendix C For evaluation, at least for FR1 MR ultra-deep sleep state, (Ramp-up and down transition energy, ramp-up time) is as follows,

A. - Alt 1: (15000, 400ms) as baseline

B. - Alt 2: (40000, 800ms)

Appendix D Company to report which alternative they use for which use cases.

Appendix E For MR, at least for FR1 evaluation,

C. - Number of SSBs for sync/re-sync for MR is up to 10

- Companies to report timeline and energy consumption

Subgroup indication up to 8 subgroups can be carried by LP-WUS for an associated PO in Rel-19.

No core-network/RAN3 impact

Define new timing relation between LP-WUS and an associated PO to support MR ramp-up time of 400 ms and 800 ms.

Note: Legacy paging occasion design is reused.

Duty-cycle of LP-WUS monitoring in idle/inactive-mode follows the paging cycle.

LP-SS periodicity should not exceed 160 ms.

Develop mechanism of offloading or relaxing MR serving cell measurement by exploiting feasibly more frequent serving cell measurement by LP-WUR.

Mechanism includes entry/exit condition for serving cell measurement by LP-WUR.

Entry/exit condition for LP-WUS monitoring is based on the outcome of serving cell measurement by LP-WUR.

Decision: The document is noted.

R1-2400066 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum Communications

R1-2400124 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2400254 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2400273 Discussion on LP-WUS Operation in IDLE/INACTIVE state TCL

R1-2400339 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2400445 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2400474 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2400496 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE, Sanechips

R1-2400570 Discussion on LP-WUS operation in Idle/Inactive modes xiaomi

R1-2400591 Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2400635 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2400671 Discussion on LP-WUS operation in IDLE/INACTIVE modes China Telecom

R1-2400685 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2400744 LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2400864 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2400884 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2400905 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2400963 LP-WUS operation in IDLE/INACTIVE mode Nokia, Nokia Shanghai Bell

R1-2401127 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2401147 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2401209 Discussion on LP-WUS operation in IDLE/INACTIVE mode Fujitsu

R1-2401235 Discussion on LP-WUS operation in RRC IDLE/INACTIVE modes ETRI

R1-2401336 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2401348 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2401453 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2401629 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement:

Multi-beam operations are supported for LP-WUS and LP-SS for idle mode.

R1-2401630 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

R1-2401631 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

Agreement

LP-WUS occasions (LOs) are defined for LP-WUS monitoring.

Each LO has one or more LP-WUS monitoring occasions (MOs), where UE can monitors for LP-WUS transmission in each of the LP-WUS MOs.

Different LP-WUS MOs may correspond to different beams in multi-beam operation
~~It is not precluded that~~ FFS whether or not each LO is defined as a time window that covers the corresponding LP-WUS MOs
FFS details

It is at least supported that a UE monitors LOs with a configured periodicity.
~~Each UE has a periodicity for LO monitoring, and it is at least supported that a UE monitors one LO per period.~~

~~FFS: A UE does not expect its LP-WUS monitoring occasions overlapping in time~~
~~FFS: monitoring of multiple more than one LOs per period e.g. if LP-WUS common to all UEs is supported or in case of eDRX (if supported)~~

FFS eDRX, if supported

Agreement

For the case where a UE supports PEI and PEI is configured by the gNB, after the UE receives LP-WUS indicating wake-up, it is up to UE implementation whether to monitor PEI or not.

Agreement

It is supported that the UE monitors the legacy PO after receiving LP-WUS indicating wake-up.

FFS: support of UE monitoring dynamic PO

Conclusion

For idle/inactive mode, how to map a UE to a subgroup ID for LP-WUS is left to RAN2 to decide.

Final summary in R1-2401872.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2400255 Discussion on LP-WUS operation in CONNECTED modes vivo

· For C-DRX based LP-WUS operation, following options are not mutually exclusive and can be supported from RAN1 perspective.

o Option 1: LP-WUS replaces Rel-16 DCP.

§ Same procedure as Rel-16 DCP is used for LP-WUS triggering PDCCH monitoring.

o Option 2: WUS is monitored at WUS MOs located within the drx-onDurationTimer and/or DRX active time.

§ UE starts PDCCH monitoring within the drx-onDurationTimer and/or DRX active time if LP-WUS addressed to UE or UE’s subgroup is detected.

§ UE terminates PDCCH monitoring and starts LP-WUS monitoring within the drx-onDurationTimer when the UE receives PDCCH skipping indication.

· From RAN1 perspective, at least support following to allow UE MR PDCCH monitoring triggered by LP-WUS without C-DRX:

o UE monitors LP-WUS at configured LP-WUS MOs which can be located at any time.

o UE starts PDCCH monitoring after MR wake up time, only when the UE detects the LP-WUS.

o UE terminates PDCCH monitoring and starts LP-WUS monitoring when the UE receives PDCCH skipping indication.

· Support UE can indicate/report one or more than one time gap used for MR transition which is defined as the time gap between the time of detecting a LP-WUS targeted for the UE and the earliest time that the MR shall be ready to monitor the PDCCH.

· Support network configures at least one time gap used for MR transition for a UE.

· In RRC CONNECTED mode, LP-WUS monitoring by a UE should be known to gNB. If the LP-WUS is not detected on a WUS monitoring occasion (MO) by the UE, UE does not wake up the MR for PDCCH monitoring.

· For UE in RRC_CONNECTED mode, option 1 that by gNB RRC signaling to activate and deactivate the procedure of PDCCH monitoring triggered by LP-WUS should be the default option.

· For UE in RRC_CONNECTED mode, further discuss whether dynamic activation/deactivation of the procedure of PDCCH monitoring triggered by WUS is needed or not, in addition to RRC configuration.

· For UE in RRC_CONNECTED mode, if dynamic activation/deactivation of WUS operation is needed, Option 2 that by gNB L1/L2 LP-WUS operation activation/deactivation signalling is the more straightforward and preferred.

· For UE in RRC_CONNECTED mode, UL transmissions such as SR, PRACH and CG PUSCH shall wake up the main radio for UL transmissions, and stop the LP-WUS monitoring .

· LP-WUS occasion(s) is determined by a WUS monitoring Periodicity, Offset, WUS monitoring Window and WUS monitoring pattern within the window where multiple LP-WUS monitoring occasions can be configured in the LP-WUS monitoring window within each period.

· The design for carrying LP-WUS content should be flexible enough to support both group common and per UE specific wake up. Up to 16 bits can be a good starting point for LP-WUS payload size.

Decision: The document is noted.

R1-2400067 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum Communications

R1-2400125 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2400304 Discussion on LP-WUS procedures in Connected mode TCL

R1-2400340 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2400446 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2400475 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2400497 Discussion on LP-WUS operation in CONNECTED mode ZTE, Sanechips

R1-2400571 Discussion on LP-WUS operation in Connected mode xiaomi

R1-2400592 Consideration on wake-up procedure in connected mode OPPO

R1-2400636 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2400672 Discussion on LP-WUS operation in CONNECTED modes China Telecom

R1-2400686 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2400745 LP-WUS operation in CONNECTED modes Samsung

R1-2400865 LP-WUS operation in CONNECTED mode Sony

R1-2400874 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2400906 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2400964 LP-WUS operation in CONNECTED mode Nokia, Nokia Shanghai Bell

R1-2401025 LP-WUS operation in CONNECTED modes Apple

R1-2401128 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2401148 LP-WUS operation in CONNECTED mode Ericsson

R1-2401236 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2401319 On LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2401337 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2401454 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2401698 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

For RRC CONNECTED mode, from RAN1 perspective, further study following LP-WUS procedures to trigger PDCCH monitoring:

Case 1: PDCCH monitoring is triggered by LP-WUS with C-DRX configuration

Option 1-1: LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer.

This option may replace DCP functionality

Option 1-2: LP-WUS monitoring outside C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

PDCCH monitoring possibly irrespective of drx-onDurationTimer

Option 1-3: LP-WUS monitoring inside C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

Case 2: PDCCH monitoring is triggered by LP-WUS without C-DRX configuration. LP-WUS can be monitored at any time according to the LP-WUS monitoring configuration

FFS duty-cycled and/or continuous LP-WUS monitoring

Combination of options in Case 1 and combination of options in Case 1 and Case 2 are not precluded.

Agreement

For RRC CONNECTED mode, maximum number of LP-WUS information bits is up to X bits.

· FFS value X, which is no more than [8 or 16]

Agreement

For RRC CONNECTED mode, minimum time gap between LP-WUS reception and MR to start PDCCH monitoring is introduced considering at least following

LP-WUS processing time
MR transition time for ramp up
Time/frequency synchronization of MR
FFS whether UE can report supported minimum time gap from candidate values

FFS: Whether the minimum time gap values can be more than one.

R1-2401836 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

For RRC CONNECTED mode, from RAN1 perspective,

· PDCCH monitoring triggered by LP-WUS is enabled/disabled by gNB RRC signaling

o FFS whether to support UE assistance.

· LP-WUS monitoring by UE is known to gNB.

o FFS whether implicit/explicit indication from UE is necessary

· In case LP-WUS monitoring is enabled, following options are further studied

o Option 1: No additional indication/condition are introduced for activation/deactivation of LP-WUS monitoring

o Option 2: Activation/deactivation of LP-WUS monitoring by gNB L1/L2 signaling with or without UE assistance.

o Option 3: Activation/deactivation of LP-WUS monitoring based on condition(s), such as timer.

o Option 4: Activation/deactivation of LP-WUS monitoring based on implicit indication/condition, e.g. UL transmission.

Final summary in R1-2401862.

RAN1#116-bis

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-240801 for detailed scope of the WI.

[116bis-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2403775 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

9.6.1 LP-WUS and LP-SS design

R1-2401982 Discussion on LP-WUS and LP-SS Design TCL

R1-2401999 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2402046 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2402114 Discussion on LP-WUS and LP-SS design Spreadtrum Communications

R1-2402193 Discussion on LP-WUS design ZTE, Sanechips

R1-2402251 Discussion on LP-WUS and LP-SS design vivo

R1-2402337 Signal design for LP-WUS and LP-SS OPPO

R1-2402392 Design of LP-WUS and LP-SS CATT

R1-2402475 Discussion on LP-WUS and LP-SS design Samsung

R1-2402519 Discussion on LP-WUS/LPSS design China Telecom

R1-2402539 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2402544 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2402574 Discussion on LP-WUS and LP-SS design CMCC

R1-2402610 Discussion on LP-WUS and LP-SS design framework for Low power WUS InterDigital, Inc.

R1-2402617 Discussion on LP-WUS and LP-SS design Everactive (Late submission)

R1-2402675 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2402728 Discussion on LP-WUS and LP-SS design Honor

R1-2402740 Discussion on LP-WUS and LP-SS design Sharp

R1-2402760 Discussion on LP-WUS and LP-SS design NEC

R1-2402890 LP-WUS and LP-SS design Apple

R1-2403453 LP-WUS and LP-SS design Nokia (rev of R1-2402906)

R1-2402952 On LP-WUS and LP-SS designs MediaTek

R1-2402976 LP-WUS and LP-SS design Sony

R1-2403418 Discussion on LP-WUS and LP-SS design Lenovo (rev of R1-2403105)

R1-2403126 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2403203 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2403253 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2403276 LP-WUS and LP-SS design Ericsson

R1-2403376 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2403554 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

For OOK-4 with M >1, support M=2 & M=4 (working assumption) for LP-WUS.

· FFS whether value of M depends on SCS

· FFS M=1 for OOK-4

Agreement

For evaluation purpose on LP-WUS, companies report the overlaid OFDM sequence(s), including:

Sequence(s) generation and how sequence(s) map in time or frequency domain (including any details with multiplexing and IFFT).
Number of candidate overlaid OFDM sequences used for information conveying

Including details on whether the number of candidate overlaid sequences is per OFDM symbol or per OOK symbol

How the proposed sequence design is processed by OFDM-based LP-WUR, e.g., in time domain or in frequency domain or in both time and frequency domain.

Agreement

Support to specify multiple binary LP-SS sequences for the ‘ON-OFF’ pattern:

The LP-SS sequence used in a cell is

Option 1: a sequence is configured
Option 2: a sequence is determined by predefined rule
FFS: Whether both options will be supported or only one will be supported

FFS: the number of LP-SS sequences
Note: Multiple sequences are used to differentiate LP-SS from different cells

R1-2403616 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Wednesday session

Agreement

From RAN1 perspective, support X PRBs for LP-WUS and LP-SS with SCS 30kHz (blanked guard RBs are not included) for a channel bandwidth equal or larger than 5MHz.

X to be down-selected between 11 and 12 PRBs
FFS the number of PRBs for 15kHz
FFS if other number of PRBs needed, for LP-SS and LP-WUS with a channel bandwidth equal or less than 5MHz

FFS: Whether the above is applicable to FR2.

Agreement

For timing error evaluation purpose, the following two options for residual frequency error are considered:

· Option 1: The maximum frequency error (Fe) of RTC/oscillator is assumed, companies report Fe value and the applied LP-WUR type.

· Option 2: The residual frequency error (Fr) after frequency error correction/clock calibration by LR or after assistance from MR is assumed, companies report Fr value, how to achieve it and the applied LP-WUR type.

Agreement

For frequency error evaluation purpose, the following two options for residual frequency error are considered:

· Option 1: The maximum frequency error (Fe) of oscillator is assumed, companies report Fe value and the applied LP-WUR type.

· Option 2: The residual frequency error (Fr) after frequency error correction by LR or after assistance from MR is assumed, companies report Fr value, how to achieve it and the applied LP-WUR type.

Working assumption

Support the following options for LP-SS

Option 1: OOK-1
Option 2: OOK-4 with M=2,4, FFS:1,8,16

FFS whether value of M depends on SCS

The SCS of a CP-OFDM symbol used for LP-SS generation is the same as that used for LP-WUS generation

FFS how OOK-1 and OOK-4 are specified

R1-2403751 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Agreement

Regarding the LP-WUS information for idle/inactive UEs, at least consider the following：

· Option 1: A bitmap with each bit corresponding to [one or more] subgroups

· Option 2: A codepoint value corresponding to one or more subgroup(s)

· Option 3: Multiple codepoint values with each corresponding to one or more subgroup(s)

· Combination of above options are not precluded

· FFS how to carry LP-WUS information, e.g., by encoded bits (with/without CRC) and/or by OOK sequence selection for ‘ON-OFF’ pattern for OOK symbols of LP-WUS.

· FFS how to carry LP-WUS information by overlaid OFDM sequences.

o It doesn’t preclude considering the configuration where a single candidate overlaid OFDM sequence is used

· Other options are not precluded

Agreement

Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs, at least consider the following：

· Option 1: A bitmap with each bit corresponding to [one or more] UEs

· Option 2: A codepoint value corresponding to one or part of UE identity, e.g., C-RNTI

· Option 3: A codepoint value corresponding to [one or more] UEs

· Option 4: Multiple codepoint values with each corresponding to [one or more] UE(s)

· Option 5: Multiple bit blocks with each corresponding to [one or more] UE(s)

· Combination of above options are not precluded.

· FFS how to carry LP-WUS information, e.g, by encoded bits (with/without CRC) and/or by OOK sequence selection for ‘ON-OFF’ pattern for OOK symbols of LP-WUS.

· FFS how to carry LP-WUS information by overlaid OFDM sequences.

o It doesn’t preclude considering the configuration where a single candidate overlaid OFDM sequence is used

· FFS details of LP-WUS information to trigger PDCCH monitoring (e.g. whether above is applicable to one or more serving cells)

Conclusion:

For calibration purposes, companies are encouraged to report the SNR to achieve the coverage of PUSCH for message3, at least with the following assumptions:

· Carrier frequency: 2.6 GHz

· The number of Tx chains: 1

· MIL of MSG 3: use the average one in R17 coverage, i.e.,153.51 dB for non-redcap UE

· Transmit antenna gain correction factors for WUS: up to company report

· Noise Figure: All three values +2dB, +5dB, +8dB on top of NF of MR (7dB) are to be reported, SNR for different assumptions on NF are determined separately

Agreement

For the purpose of further study and evaluation in RAN1, the following candidate sequences for the overlaid OFDM sequence are considered:

Gold sequence
M-sequence
ZC sequence
Chirp sequence
Walsh sequence
Golay sequence
Kasami sequence
Low density sequence
DFT/FFT sequence
QAM symbol-based sequence
Combinations and optimizations of above are not precluded

Companies are encouraged to provide an assessment on performance, required complexity, and power consumption to support their preferred sequence. Companies are encouraged to provide details on their preferred sequence (e.g. references).

Agreement

Regarding the overlaid OFDM sequence(s) of LP-WUS, consider the following options:

Option 1: Single overlaid sequence is on each OOK ‘ON’ symbol or OFDM symbol duration. OFDM-based LP-WUR can obtain the whole information bits by the presence of the overlaid sequence.
Option 1-2: The overlaid OFDM sequence is pre-determined from multiple sequences. This sequence carry NO information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by the OOK ON/OFF pattern.
Option 2: One sequence is selected from multiple candidates overlaid OFDM sequences on each OOK ‘ON’ symbol or OFDM symbol duration, and OFDM-based LP-WUR obtain LP-WUS information at least by overlaid OFDM sequence(s). Consider the following two sub-options.

Option 2-1: The overlaid OFDM sequence(s) carry part of information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by OFDM sequence(s) and location of the OFDM sequence(s)/OOK symbols.
Option 2-2: The overlaid OFDM sequence(s) carry all information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by the overlaid OFDM sequence(s)

Option 3: One sequence is selected from multiple candidates overlaid OFDM sequences on one or more OOK ‘ON’ symbols, and OFDM-based LP-WUR obtain LP-WUS information at least by overlaid OFDM sequence(s).
Option 4: Use of modulated overlay sequence with constellation point: overlay sequence acting as a spreading sequence and constellation point carrying information for OFDM-based LP-WUR.

Other options are not precluded.

Final summary in R1-2403770.

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2401983 Discussion on LP-WUS Operation in IDLE/INACTIVE modes TCL

R1-2402000 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2402047 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2402115 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum Communications

R1-2402194 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE, Sanechips

R1-2402252 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2402338 Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2402393 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2402476 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2402520 Discussion on LP-WUS operation in IDLE/INACTIVE modes China Telecom

R1-2402545 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2402575 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2402611 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2402676 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2402741 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2402761 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2402835 Discussion on LP-WUS operation in IDLE/INACTIVE mode Fujitsu

R1-2402891 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2402907 LP-WUS operation in ILDE/Inactive mode Nokia

R1-2402953 On LP-WUS operation in IDLE/INACTIVE modes MediaTek

R1-2402977 LP-WUS operation in IDLE / INACTIVE mode Sony

R1-2403027 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2403106 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2403127 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2403138 Views on LP-WUS operation in IDLE/INACTIVE modes KT Corp.

R1-2403204 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2403254 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2403277 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2403375 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2402893 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement

For multi-beam operation of LP-WUS, UE assumes the same LP-WUS information payload is repeated in all transmitted beams corresponding to LP-WUS,

· the selection of the beam(s) for the reception of the LP-WUS is up to UE implementation.

R1-2402894 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Wednesday session

Agreement

Each LO consists of N * K LP-WUS MOs, where N is the number of beams corresponding to LP-WUS, and K is the number of LP-WUS MOs for each beam.

Option 1: K = 1
Option 2: K can be larger than or equal to 1

FFS if more than 1 LP-WUS is transmitted from the same beam, whether the information in these multiple LP-WUS is always the same or can be different

Agreement

From RAN1 perspective, at least the following metrics can be supported for RRM serving cell measurement performed by OOK-based receiver based on LP-SS:

LP-RSRP

LP-RSRP is the linear average of received power of LP-SS in OOK ON symbols.

FFS: How to determine the received power of LP-SS in OOK ON symbols

LP-RSRQ

LP-RSRQ = LP-RSRP/LP-RSSI
For the definition of LP-RSSI for determination of LP-RSRQ, further consider the following options:

Option 1: LP-RSSI is the linear average of total received power in all LP-SS OOK symbols.
Option 2: LP-RSSI is the linear average of total received power in LP-SS OOK OFF symbols.
Option 3: LP-RSSI is the linear average of total received power in LP-SS OOK ON symbols.

FFS: LP-SINR, ~~Power ratio of OOK-ON symbol and OOK-OFF symbol~~

Note: ~~RAN1 will send an LS to RAN2 and RAN4 on the measurement metrics that can be supported from RAN1 perspective, to facilitate RAN2/RAN4 discussions~~. The exact metrics for OOK-based receiver to be used and defined in the specifications depend on the outcome of [RAN1]/RAN2/RAN4 discussions.

R1-2402895 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

Working Assumption

From RAN1 perspective, for the entry/exit conditions for LP-WUS monitoring in IDLE/inactive mode,

The UE may start LP-WUS monitoring if

the serving cell measurement performed by the MR is above entry threshold(s), if configured by the gNB~~, and/or~~
FFS other conditions, and if any, whether all or one or some of the conditions need to be satisfied

If UE starts LP-WUS monitoring, it may stop the legacy PO monitoring before UE receives LP-WUS indicating wake-up
The UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if

the serving cell measurement performed by the LR is below exit threshold(s), if configured by the gNB~~, and/or~~
FFS other conditions, and if any, whether all or one or some of the conditions need to be satisfied

FFS the serving cell measurement metrics
The entry/exit thresholds can be configured separately for different types of LR
It is left to RAN2 discussion whether the threshold(s) are always configured by the gNB.
Note: This may be revisited based on the RAN2/RAN4 discussion.

Conclusion

LP-SINR is not considered further as a metric for RRM serving cell measurement ~~for OOK-based receiver~~.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2402001 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2402116 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum Communications

R1-2402195 Discussion on LP-WUS operation in CONNECTED mode ZTE, Sanechips

R1-2402253 Discussion on LP-WUS operation in CONNECTED modes vivo

R1-2402339 Consideration on wake-up procedure in connected mode OPPO

R1-2402394 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2402477 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2402521 Discussion on LP-WUS operation in CONNECTED modes China Telecom

R1-2402546 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2402576 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2402588 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2402612 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2402677 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2402742 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2402762 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2402892 LP-WUS operation in CONNECTED modes Apple

R1-2402908 LP-WUS operation in CONNECTED mode Nokia

R1-2402954 On LP-WUS operation in CONNECTED modes MediaTek

R1-2402978 LP-WUS operation in CONNECTED mode Sony

R1-2403028 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2403037 Discussion on LP-WUS procedures in Connected mode TCL

R1-2403128 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2403205 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2403255 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2403278 LP-WUS operation in CONNECTED mode Ericsson

R1-2403517 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

Presented in Tuesday session

R1-2403713 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

· Update the following agreement in RAN1#116 in red:

Agreement

· For RRC CONNECTED mode, from RAN1 perspective, further study following LP-WUS procedures to trigger PDCCH monitoring:

o Case 1: PDCCH monitoring is triggered by LP-WUS with C-DRX configuration

§ Option 1-1: LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer.

· This option may replace DCP functionality

§ Option 1-2: LP-WUS monitoring outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

· PDCCH monitoring possibly irrespective of drx-onDurationTimer

o Option 1-2-1: PDCCH monitoring may be additionally triggered based on legacy C-DRX cycle and drx-onDurationTimer when monitoring LP-WUS

§ If this is adopted, it should be configured together with Option 1-1 to achieve power saving gain compared to legacy C-DRX

o Option 1-2-2: PDCCH monitoring is not triggered by legacy C-DRX cycle and drx-onDurationTimer when monitoring LP-WUS

§ Option 1-3: LP-WUS monitoring inside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

o ~~Case 2: PDCCH monitoring is triggered by LP-WUS without C-DRX configuration. LP-WUS can be monitored at any time according to the LP-WUS monitoring configuration~~

§ ~~FFS duty-cycled and/or continuous LP-WUS monitoring~~

· Combination of options in Case 1 ~~and combination of options in Case 1 and Case 2 are not precluded~~ should be considered.

· RAN1 does not discuss C-DRX related timers other than drx-onDurationTimer, this topic is up to RAN2

· Note: Above does not preclude to support fallback mechanism to trigger PDCCH monitoring, if any

Final summary in R1-2403714.

RAN1#117

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-240801 for detailed scope of the WI.

[117-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2405735 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

9.6.1 LP-WUS and LP-SS design

R1-2403864 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2403879 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2403948 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2404035 Discussion on LP-WUS and LP-SS design Spreadtrum Communications

R1-2404059 Discussion on LP-WUS and LP-SS Design TCL

R1-2404124 Discussion on LP-WUS and LP-SS design Samsung

R1-2404186 Discussion on LP-WUS and LP-SS design vivo

R1-2404296 LP-WUS and LP-SS design Apple

R1-2404312 Discussion on LP-WUS and LP-SS design framework for Low power WUS InterDigital, Inc.

R1-2404320 Discussion on LP-WUS and LP-SS design Everactive (Late submission)

R1-2404410 Design of LP-WUS and LP-SS CATT

R1-2404465 Discussion on LP-WUS and LP-SS design CMCC

R1-2404509 LP-WUS and LP-SS design Sony

R1-2404563 Discussion on LP-WUS design ZTE, Sanechips

R1-2404579 Discussion on LP-WUS and LP-SS design HONOR

R1-2404627 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2404664 Discussion on LP-WUS and LP-SS design NEC

R1-2405655 LP-WUS and LP-SS design Nokia (rev of R1-2404705)

R1-2404760 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2404852 Signal design for LP-WUS and LP-SS OPPO

R1-2404897 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2404942 Discussion on LP-WUS and LP-SS design Lenovo

R1-2404966 Discussion on LP-WUS and LP-SS design Sharp

R1-2405051 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2405073 LP-WUS and LP-SS design MediaTek Inc.

R1-2405374 LP-WUS and LP-SS design Ericsson (rev of R1-2405108)

R1-2405164 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2405254 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2405499 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

Support overlaid OFDM sequence based on existing NR sequence type for LP-WUS

Down select among gold sequence, m sequence and ZC sequence

FFS the overlaid OFDM sequence is time or frequency domain sequence.
FFS how to reuse the existing sequences
Note: Strive to minimize the impact on OOK detection performance

If overlaid OFDM sequence is supported for LP-SS, the same sequence type is used for both LP-SS and LP-WUS

Agreement

For the LP-SS sequence used in a cell,

· Option 1: the information necessary for determining the sequence is explicitly configured

· FFS: Additional support of determining the sequence by predefined rule without configuration

R1-2405519 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Wednesday session

Agreement (further amended as shown in red on Friday)

The LP-WUS and LP-SS design assumes the residual frequency error after frequency error correction without considering impact of drift, is up to X ppm for OOK-based LP-WUR.

FFS X which is no larger than 20ppm
~~FFS: Initial frequency error assumption: 200ppm~~

· Initial frequency error assumption: up to company report

For the overlaid OFDM sequence design of LP-WUS, it is assumed that the residual frequency error for OFDM-based LP-WUR after frequency error correction without considering impact of drift is not larger than Y.

FFS Y which is no larger than 20ppm and lower than X
~~FFS: Initial frequency error assumption: 200ppm~~

· Initial frequency error assumption: up to company report

Agreement

For overlaid OFDM sequence(s) for LP-WUS in time or frequency domain, down-selection from the following:

Option 1-1: overlaid sequence(s) are the sequence(s) of an OOK on symbol before DFT/LS processing

The length of overlaid sequence(s) depends on the number of REs used for LP-WUS and the value of M

Option 1-2: overlaid sequence(s) are the sequence(s) of an OFDM symbol before DFT/LS processing

The length of overlaid sequence(s) depends on the number of REs used for LP-WUS

Option 2: overlaid sequence(s) are the sequence(s) of an OFDM symbol before IFFT processing

The length of overlaid sequence(s) depends on the number of REs used for LP-WUS

Option 3: overlaid sequence(s) are the sequence(s) of an OOK on symbol in time domain after IFFT processing

The length of overlaid sequence(s) depends on IFFT size and the value of M

FFS: same or different options are applied for OOK-1 and OOK-4 M>1.

Agreement (further amended as shown in red on Friday)

Update agreement in last meeting as below:

From RAN1 perspective, support X PRBs for LP-WUS and LP-SS with SCS 30kHz (blanked guard RBs are not included) for a channel bandwidth equal or larger than 5MHz

· X ~~to be down-selected between~~ = 11 ~~and 12~~ PRBs

· ~~FFS the number of PRBs for 15kHz is 11 PRBs or 22 PRBs?~~

· FFS the number of PRBs for 15kHz

· FFS if other number of PRBs needed, for LP-SS and LP-WUS with a channel bandwidth equal or less than 5MHz

FFS: Whether the above is applicable to FR2

R1-2405600 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

R1-2405645 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday session

Agreement

Further down-select the number of binary LP-SS sequences for the ‘ON-OFF’ pattern:

Agreement

For the binary LP-SS sequence type for the ‘ON-OFF’ pattern in a LP-SS, further down-selection from the following:

Gold sequence
M sequence
Computer searched sequence
FFS: the length of LP-SS sequence

R1-2405708 Summary #5 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Observation

The following SNR values for LP-WUR are reported by companies to achieve coverage of PUSCH for message3 for difference noise figures for calibration purposes:

NF of LR = NF of MR+ 8dB: the reported SNR value range is [-9.05,2.94] dB
NF of LR = NF of MR+ 5dB: the reported SNR value range is [-6.5, 5.58] dB
NF of LR = NF of MR+ 2dB: the reported SNR value range is [-4.04,7.95] dB
Note 1: The above is observed based on the following assumptions used for calibration:

o Carrier frequency: 2.6 GHz

o The number of Tx chains: 1

o MIL of MSG 3: use the average one in R17 coverage, i.e.,153.51 dB for non-redcap UE

o Transmit antenna gain correction factors for WUS: up to company report

o Noise Figure: All three values +2dB, +5dB, +8dB on top of NF of MR (7dB) are to be reported, SNR for different assumptions on NF are determined separately

Agreement

For evaluation of LP-WUS and LP-SS design to achieve coverage of PUSCH for message3 from RAN1 perspective, at least the following SNR values should be considered:

SNR=-3dB for NF of LR = NF of MR+ 8dB
SNR= -0.5dB for NF of LR = NF of MR+ 5dB
SNR=2dB for NF of LR = NF of MR+ 2dB
Note 1: The NF of MR is assumed as 7dB

Agreement

For RRC idle/inactive state, down-select among the following options for at least indicating subgroup information using LP-WUS:

Option 1: A LP-WUS indicates a bitmap with each bit corresponding to one subgroup of N subgroups for part of, one or more PO(s), e.g., N is 8~16, 24

Number of information bits for a LP-WUS is at least N, single LP-WUS to wake up one or more subgroups

Option 2: A LP-WUS indicates a codepoint value corresponding to one or more subgroup(s) from N subgroups for part of, one or more POs, e.g., N is 8~256

Number of information bits for a LP-WUS is at least ceil (log2(X1)), where X1 is the number of codepoints indicating one or more subgroups. X1 is reported by companies, X1 could be smaller, equal to or larger than N.

Option 3: A LP-WUS indicates multiple codepoint values with each corresponding to one or more subgroup(s) from N subgroups for part of, one or more POs, e.g., N is 8~256

Number of information bits for a LP-WUS is at least K*ceil (log2(X2)), where X2 is the number of codepoints indicating one or more subgroups. X2 is reported by companies, X2 could be smaller, equal to or larger than N.
K is the number of multiple codepoint values in a LP-WUS where K is larger than 1

How to satisfy FAR is reported by companies, e.g., FEC/CRC
Note: multiple TDMed LP-WUSs can be used to support more subgroups for each option.
Note: Y% effective paging rate per PO is reported by companies
The followings are considered when down-select among options:

The number of supported UE subgroups per PO: M
Average network overhead to indicate the number of UE subgroups M per PO
False wake up rate due to subgroup-based indication, which will impact the power saving gain
Paging latency
Note: Coverage target shall be met under 1%BLER, 1% FAR (for false alarm from noise)

Final summary in R1-2405732.

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2403865 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2403949 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2404036 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum Communications

R1-2404125 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2404136 Discussion on LP-WUS Operation in IDLE/INACTIVE state TCL

R1-2404187 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2404297 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2404313 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2404411 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2404466 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2404510 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2404564 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE, Sanechips

R1-2404628 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2404665 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2404706 LP-WUS operation in IDLE/Inactive mode Nokia

R1-2404761 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2404782 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2404805 Discussion on LP-WUS operation in IDLE/INACTIVE mode Fujitsu

R1-2404853 Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2404898 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2404943 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2404967 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2405052 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2405074 LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

R1-2405109 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2405165 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2405180 Discussion on LP-WUS operation in IDLE/INACTIVE modes KT Corp.

R1-2405253 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2404299 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Conclusion

Regarding the “FFS: How to determine the received power of LP-SS in OOK ON symbols” for LP-RSRP, no additional work in RAN1.

R1-2404300 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Wednesday session

Agreement

It is supported that UEs monitoring the same PO are divided into multiple subgroups, where LP-WUS can provide wake-up indication for each subgroup. Consider the following options:

Option 1: UEs monitoring the same PO monitor the same LO
Option 2: UEs corresponding to different POs monitor the same LO
Option 3: UEs monitoring the same PO are divided into multiple sets of subgroups, with UEs within each set of subgroups monitoring the same LO.
Combinations of the above options can be considered.

R1-2404301 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Agreement

For LP-SS based LP-RSRQ, LP-RSRP and LP-RSSI are measured within the same bandwidth.

Agreement

For LP-RSSI definition for LP-RSRQ, down-select between the following two options:

Option 1: LP-RSSI is the linear average of total received power in ON and OFF LP-SS OOK symbols.

Note: Above does not constrain LP-SS sequence design for OOK.

Working Assumption

From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.

· Above is applicable for both time-domain processing or frequency-domain processing

· Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications

R1-2405681 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

Agreement

For idle/inactive mode, the maximum number of information bits (excluding CRC) in a LP-WUS is Z, where Z <= [8 or 16].

FFS the exact value of Z

Agreement

For idle/inactive mode, the maximum number of subgroups per PO is X, where 8 <= X <= 256.

FFS the exact value of X.

Final summary in R1-2405682.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2403950 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2404001 Discussion on LP-WUS procedures in Connected mode TCL

R1-2404037 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum Communications

R1-2404126 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2405512 Discussion on LP-WUS operation in CONNECTED modes vivo (rev of R1-2404188)

R1-2404298 LP-WUS operation in CONNECTED modes Apple

R1-2404314 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2404412 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2404440 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2404467 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2404511 LP-WUS operation in CONNECTED mode Sony

R1-2404565 Discussion on LP-WUS operation in CONNECTED mode ZTE, Sanechips

R1-2404629 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2404666 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2404707 LP-WUS operation in CONNECTED mode Nokia

R1-2404762 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2404783 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2404854 Consideration on wake-up procedure in connected mode OPPO

R1-2404899 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2404968 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2405053 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2405075 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2405110 LP-WUS operation in CONNECTED mode Ericsson

R1-2405508 LP-WUR operation in connected mode Qualcomm Incorporated (rev of R1-2405166)

R1-2405471 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Tuesday session

Agreement

For RRC CONNECTED mode, support UE capability report for determination of minimum time gap between LP-WUS reception and MR to start PDCCH monitoring.

· FFS: exact value(s) of the minimum time gap

· FFS: support of multiple minimum time gaps

· FFS whether the reported value includes the duration for time/frequency synchronization of MR

R1-2405592 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

For LP-WUS monitoring in RRC CONNECTED mode, a LP-WUS is QCLed with existing NR signal/channel/CORESET for the TCI state

· FFS which existing NR signal/channel/CORESET is the QCL source of LP-WUS

· FFS exact definition of QCL relationship between LP-WUS and existing NR signal/channel/CORESET

Agreement

LP-WUS monitoring occasions (MOs) are configured by RRC, where UE can monitor for LP-WUS transmission in RRC CONNECTED mode.

FFS whether to define a time window for Mos
It is at least supported that a UE can monitor MOs with a periodicity.

FFS details of the periodicity, e.g. derived from DRX cycle, separately configured

R1-2405659 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

Study whether/how LP-WUS works when UE is configured with CA in RRC CONNECTED mode

FFS: The cell(s) where PDCCH monitoring triggered by a LP-WUS is applicable

Option 1: one or more serving cells based on gNB indication/configuration
Option 2: all activated serving cells
Note: other options are not precluded

Agreement

For RRC CONNECTED mode, LP-WUS can be configured without following existing features.

Rel-16 DCP
Rel-17 PDCCH skipping
Rel-17 SSSG switching
Rel-18 cell DTX

Further study whether/how LP-WUS works with following existing features (PDCCH skipping, SSSG switching, cell DTX)

Final summary in R1-2405721.

RAN1#118

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-240801 for detailed scope of the WI.

[118-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.6.1 LP-WUS and LP-SS design

R1-2405806 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2405867 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2405919 Discussion on LP-WUS and LP-SS design Spreadtrum Communications

R1-2405966 Preliminary Assessment on Low-Power Wake-Up Receiver Tejas Networks Limited

R1-2405996 Discussion on LP-WUS and LP-SS design CMCC

R1-2406083 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2406104 Discussion on LP-WUS and LP-SS Design TCL

R1-2406193 Discussion on LP-WUS and LP-SS design vivo

R1-2406222 Signal design for LP-WUS and LP-SS OPPO

R1-2406295 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2406379 Design of LP-WUS and LP-SS CATT

R1-2406412 Discussion on LP-WUS design ZTE Corporation, Sanechips

R1-2406422 LP-WUS and LP-SS design Nokia

R1-2406480 LP-WUS and LP-SS design Sony

R1-2406498 Discussion on LP-WUS and LP-SS design framework for Low power WUS InterDigital, Inc.

R1-2406504 Discussion on LP-WUS and LP-SS design Everactive

R1-2406537 Discussion on LP-WUS and LP-SS design NEC

R1-2406583 Discussion on LP-WUS and LP-SS design HONOR

R1-2406597 Discussions on LP-WUS and LP-SS design Ruijie Networks Co. Ltd

R1-2406611 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2406661 Discussion on LP-WUS and LP-SS design Samsung

R1-2406762 LP-WUS and LP-SS design MediaTek Inc.

R1-2406785 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2406814 Discussion on LP-WUS and LP-SS design Lenovo

R1-2406850 LP-WUS and LP-SS design Apple

R1-2406881 Discussion on LP-WUS and LP-SS design Sharp

R1-2406941 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2407040 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2407059 LP-WUS and LP-SS design Ericsson

R1-2407136 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2407287 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

For RRC idle/inactive state, support the following option for at least indicating subgroup information using LP-WUS:

Option 2: A LP-WUS indicates a codepoint value corresponding to one or more subgroup(s) from N subgroups for part of, one or more POs

UE monitoring one or more MOs (up to X MOs) for the same beam within an LO is supported

Value of X is larger than 1. FFS on additional details of X.

Agreement

Confirm the Working Assumption that OOK-4 with M=4 for 15KHz SCS is supported for LP-WUS.

Agreement

For OOK-4 with M >1, support M=2 & M=4 ~~(working assumption)~~ for LP-WUS.

- M=4 for 15KHz SCS

- M=4 for 30KHz SCS (working assumption)

- FFS M=1 for OOK-4

R1-2407356 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Wednesday session

Agreement

Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs (for non-CA case), select at least one from the following

· Option 1: A bitmap with each bit corresponding to [one or more] UEs

· Option 3: A codepoint value corresponding to [one or more] UEs

· FFS details for extension of option 1 and/or 3 when UE is configured with CA

Agreement

For overlaid OFDM sequences for LP-WUS, support option 1-1 for OOK-4 M>1.

· Option 1-1: overlaid sequence(s) are the sequence(s) of an OOK on symbol before DFT/LS processing

Agreement

For overlaid OFDM sequences for LP-WUS, further down-selection between following two options for OOK-1 and OOK-4 with M=1(if supported)

· Option 1-1: Overlaid sequence(s) are the sequence(s) of an OOK on symbol before DFT/LS processing

· Option 2: Overlaid sequence(s) are the sequence(s) of an OFDM symbol before IFFT processing

· Note: Different options for OOK-1 and OOK-4 with M=1 (if supported) is not precluded – in which case, it should be deemed necessary

Agreement

The number of binary LP-SS sequences is 4.

R1-2407420 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

Presented in Thursday session.

R1-2407491 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Agreement

To determine the binary sequences for LP-SS, the evaluation assumes the following:

Sync accuracy: timing estimation error smaller than T us for P=90 % of the time for at least SNR=-3dB and SNR=-6dB (lower priority),

T=2us(optional), 5us for OOK-1.
T=1us(optional), 2us for OOK-4 with M=2.
T=0.5us(optional), 1us for OOK-4 with M=4.
Other values of SNR, T, M are up to company report.
Additionally, companies can submit results on SINR with details on how the interference was modelled.
Assume one-shot estimation.
The time error is based on 20ppm maximum frequency error for the detection of the first LP-SS.
Note: Companies can assume other values inside of 20ppm maximum as long as the values are justified.

RRM measurement accuracy: measurement accuracy within range ± XdB for Q=90% measurements based on Y LP-SS samples within a period comparable to Z=the length of I-DRX cycle that is larger or equal to 1.28s for at least SNR=-3dB and SNR=-6dB (lower priority), X, Y, and Z is up to company report, other values of SNR are up to company report.

As a starting point, the time error is based on 5-10ppm residual frequency error.
Note: 5-10ppm assumes frequency error correction is performed, e.g., RTC calibration and/or MR assistance.
Note: Companies can assume other values outside of 5-10ppm as long as the values are justified.

The frequency error: up to company report.
Sampling rate: 3.84MHz (optional) or 7.68MHz assumed for 30kHz SCS.
Channel: AWGN and TDL-C 300ns is assumed.
Consider cross-correlation for 4 binary sequences under time and frequency error.
Companies are encouraged to provide details on other additional simulation assumptions, high level description of their receiver algorithm, and assessment on power consumption.

Agreement

For OOK-based LP-WUR, the LP-WUS design assumes the following:

As starting point, the time error is based on the 5-10ppm residual frequency error after frequency error correction without considering impact of drift.
The frequency error: up to company report.
Note: 5-10ppm assumes frequency error correction is performed, e.g., RTC calibration and/or MR assistance.
Note: Companies can assume other values outside of 5-10ppm as long as the values are justified.

Agreement

As a starting point, for both time error and frequency error, the overlaid OFDM sequence design of LP-WUS assumes that the residual frequency error is 0.1-5ppm for OFDM-based LP-WUR after frequency error correction without considering impact of drift.

Note: Companies can use any value within the above range with justification on the value (including impact on power consumption).

Agreement

Support Manchester coding for LP-WUS

· FFS other coding schemes.

Final summary in R1-2407492.

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2405807 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2405868 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2405920 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum Communications

R1-2405997 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2406105 Discussion on LP-WUS Operation in IDLE/INACTIVE modes TCL

R1-2406194 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2406223 Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2406296 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2406380 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2406413 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE Corporation, Sanechips

R1-2406423 LP-WUS operation in IDLE/INACTIVE mode Nokia

R1-2406481 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2406499 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2406519 Discussion on LP-WUS operation in IDLE/INACTIVE modes Fujitsu

R1-2406538 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2406567 Discussion on LP-WUS operation in IDLE/INACTIVE modes KT Corp.

R1-2406612 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2406662 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2406735 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2406763 LP-WUS operation in IDLE INACTIVE modes MediaTek Inc.

R1-2406786 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2406815 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2406851 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2406882 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2406942 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2407041 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2407060 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2407135 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2406853 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement

The definitions of LP-RSRP and LP-RSSI for LP-RSRQ are updated as follows:

· LP-RSRP is the linear average of received power of LP-SS in OOK ON symbols over the frequency resources defined by the number of REs that carry LP-SS.

· LP-RSSI is the linear average of total received power in ON and OFF LP-SS OOK symbols over the frequency resources defined by the number of REs that carry LP-SS.

Agreement

At least support 1:1 association between LP-WUS MO(s)/LP-SS transmissions and SSB beams.

R1-2406854 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Wednesday session

Agreement

For the wake-up delay, consider the following options:

Option 2: UE reports one value from X candidate values for the wake-up delay via UE capability reporting.

FFS: X is 2, 3, 4

Above applies for IDLE/INACTIVE mode.

Definition of wake-up delay: Minimum gap time between LP-WUS reception and MR to start PDCCH monitoring.

Conclusion

There is no consensus in RAN1 on the support of dynamic PO.

R1-2406855 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Agreement

For the maximum number of subgroups per PO (X), down-select from the following options in RAN1#118bis:

· Option 1: X = 8

· Option 2: X = 16

· Option 3: X = 32

· Option 4: X = 64

· Option 5: X = 128

· Option 6: X = 256

For decision in RAN1#118bis, companies are encouraged to provide the maximum number of information bits per LP-WUS (Z), the number of OFDM symbols occupied by LP-WUS per MO, the number of MOs for their preferred option.

Agreement

On the LO configuration for iDRX, offset value(s) between a LO and a reference PO/PF is/are configured.

FFS: one or multiple offset values, and if multiple offset values are supported, how a UE decides which value to use
FFS: the exact definition of the reference PF/PO and the detailed procedure for UE to determine the LO(s) corresponding to Option 1, 2, or 3 (if supported)
(Working Assumption) For each UE, the periodicity of LO is the same as its iDRX cycle.
If a UE receives a wake-up indication in a LP-WUS, consider the following alternatives.

Alt 1: it monitors the PO associated with the offset.
Alt 2: it monitors the first PO after its reported wake-up delay.
Other alternatives are not precluded.

Note: The PO mentioned above refers to legacy PO configured for the UE.

R1-2407506 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

Agreement

Send an LS to RAN2 and RAN4 to convey the following

In RAN1, the common understanding is that UE may not support LP-WUS reception on all the bands supported by the UE. Request RAN2 and RAN4 to check if there is any issue and specification support needed for IDLE/INACTIVE UEs.

R1-2407558 Draft LS on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Decision: The draft LS is endorsed. Final LS is approved in in R1-2407559.

Conclusion

RAN1 will not initiate work on entry/exit conditions based on RRM measurement and RRM measurement offloading/relaxation conditions unless triggered by RAN2 and RAN4.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2405869 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2405921 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum Communications

R1-2405998 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2406195 Discussion on LP-WUS operation in CONNECTED modes vivo

R1-2406224 Further consideration on LP-WUS operation in connected mode OPPO

R1-2406297 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2406381 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2406390 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2406414 Discussion on LP-WUS operation in CONNECTED mode ZTE Corporation, Sanechips

R1-2406424 LP-WUS operation in CONNECTED mode Nokia

R1-2406482 LP-WUS operation in CONNECTED mode Sony

R1-2406500 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2406510 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2406539 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2406613 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2406663 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2406736 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2406764 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2406852 LP-WUS operation in CONNECTED modes Apple

R1-2406883 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2406943 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2407042 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2407061 LP-WUS operation in CONNECTED mode Ericsson

R1-2407104 Discussion on LP-WUS procedures in Connected mode TCL Late submission

R1-2407301 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

Presented in Tuesday session.

R1-2407378 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

For option 1-2 of LP-WUS CONNECTED mode operation, the followings are assumed from RAN1 perspective.

LP-WUS monitoring outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.
UE is configured with legacy C-DRX configurations as Rel-18.
UE is expected to be configured with LP-WUS monitoring configuration (periodicity and offset can be different from those from C-DRX configuration).

FFS potential restriction for LP-WUS configuration in relation with C-DRX configuration.

LP-WUS triggers the start of a timer during which UE monitors PDCCH.

FFS the timer is existing timer and/or new timer.

UE PDCCH monitoring behaviors related to other legacy DRX timers are not affected.

drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL.

No impact on RRM/RLM/BFD measurement requirements is assumed.
For periodic CSI/L1-RSRP reporting, UE can be configured with one of the following (same as Rel-16 DCP and option 1-1).

Periodic CSI/L1-RSRP is not reported if UE is not indicated to wake-up.
Periodic CSI/L1-RSRP is periodically reported regardless if UE is indicated to wake-up or not.

UE PDCCH monitoring is not triggered by legacy C-DRX cycle and drx-onDurationTimer when monitoring LP-WUS.

Working Assumption

From RAN1 perspective, for RRC CONNECTED mode, PDCCH monitoring is triggered by LP-WUS with C-DRX configuration

· Support Option 1-1: LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer.

· Support Option 1-2: LP-WUS monitoring outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

· FFS whether/how to support both Option 1-1 and Option 1-2 simultaneously configured for the same UE.

Note: Above can be revisited considering RAN2 decisions.

R1-2407516 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

Select one of the following alternatives in RAN1#118bis:

Alt 1: For RRC CONNECTED mode, UE reports one value for each SCS from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting.

· FFS: X

· FFS: definition of reported value

Alt2: For RRC CONNECTED mode, UE reports multiple values for each SCS from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting.

· FFS: X

· FFS: definition of reported value

· Different minimum time gaps correspond to different sleep states

· Companies are encouraged to details on how the reported values are to be used by the network

Agreement

LP-WUS is at least supported for the case where a UE is configured with CA in RRC CONNECTED mode

· FFS: DC

Agreement

For LP-WUS monitoring in RRC CONNECTED mode, SSB and/or CSI-RS can be the QCL source of LP-WUS

· FFS applicable QCL type(s)

Final summary in R1-2407517.

RAN1#118-bis

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-241824 for detailed scope of the WI.

[118bis-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2409307 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

For information.

9.6.1 LP-WUS and LP-SS design

R1-2407614 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2407634 Discussion on LP-WUS and LP-SS Design TCL

R1-2407664 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2407714 Discussion on LP-WUS and LP-SS design Spreadtrum Communications

R1-2407869 Discussion on LP-WUS and LP-SS design vivo

R1-2407913 Discussion on LP-WUS and LP-SS design CMCC

R1-2407977 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2408055 Design of LP-WUS and LP-SS CATT

R1-2408074 Discussion on LP-WUS design ZTE Corporation, Sanechips

R1-2408129 Signal design for LP-WUS and LP-SS OPPO

R1-2408217 Discussion on LP-WUS and LP-SS design NEC

R1-2408236 Discussion on LP-WUS and LP-SS design HONOR

R1-2408253 Discussion on LP-WUS and LP-SS design Sharp

R1-2408271 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2408280 Discussion on LP-WUS and LP-SS design framework for Low power WUS InterDigital, Inc.

R1-2408344 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2408399 LP-WUS and LP-SS Design Everactive

R1-2408416 LP-WUS and LP-SS design Sony

R1-2408476 LP-WUS and LP-SS design Apple

R1-2408537 LP-WUS and LP-SS design Nokia

R1-2408654 Discussion on LP-WUS and LP-SS design Samsung

R1-2408679 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2408691 LP-WUS and LP-SS design MediaTek Inc.

R1-2408794 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2408820 LP-WUS and LP-SS design Ericsson

R1-2408858 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2408918 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2408968 Discussion on LP-WUS and LP-SS design Lenovo

R1-2409089 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Monday session

Working Assumption

For overlaid OFDM sequences for LP-WUS in time or frequency domain, down-select between following two options for OOK-1 and OOK-4 M=1

· Option 1-1(compromised): overlaid sequence(s) are the sequence(s) of an OOK on symbol before DFT/LS processing for OOK-4 with M=1.

o ZC sequence in time domainàDFT/LSàIFFT to result in a frequency domain sequence that is ZC sequence or a sequence that is close to ZC sequence, no additional operation

§ It doesn’t preclude additional operation for OOK-4 with M>1.

§ DFT size is 2^n

Note1: OOK-1 is considered as specific case of OOK-4 with M=1.

Note: Concerns were raised by Ericsson and CATT that the above is not beneficial in terms of implementation complexity.

Agreement

In case of overlaid OFDM sequence carrying information, support option 2:

· Option 2: One sequence is selected from multiple candidates overlaid OFDM sequences on each OOK ‘ON’ symbol, and OFDM-based LP-WUR obtain LP-WUS information at least by overlaid OFDM sequence(s). Consider the following two sub-options for potential down-selection.

o Option 2-1: The overlaid OFDM sequence(s) carry part of information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by OFDM sequence(s) and location of the OFDM sequence(s)/OOK ‘ON’ symbols.

o Option 2-2: The overlaid OFDM sequence(s) carry all information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by the overlaid OFDM sequence(s)

Note: the overlaid OFDM sequence in each OOK ‘ON’ symbol can be different according to information bits to be carried by the overlaid OFDM sequence within the LP-WUS.

Agreement

From RAN1 perspective, support X=11 PRBs for LP-WUS and LP-SS with SCS 15kHz (blanked guard RBs are not included) for a channel bandwidth equal or larger than 5MHz.

R1-2409090 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

To determine the binary sequences for LP-SS, for each M value, down-select the sequence length L from the corresponding candidate values:

M=1, L= {4,6,8}
M=2, L= {8,12,16,24}
M=4, L= {16,24,32,56}
FFS whether one or more than one L value (s) applied to each of M values M=1,2,4
FFS the L values applied to other applicable SCS(s)
FFS the L values if other M values in addition to M=1,2,4 are supported.
FFS whether the time estimation averaged across multiple LP-SS occasions is applied
Note 1: with sequence length L, it includes Manchester coding (if supported for LP-SS)
Note 2: This doesn’t preclude any of three agreed sequence types

Above applies at least for both 15kHz and 30kHz.

Agreement

For LP-SS periodicity, support at least 320ms.

· FFS: 80ms,160ms, 640ms,1280ms, 2560ms, 5120ms, 10240ms

Agreement

For overlaid OFDM sequence at least for LP-WUS,

For OOK-4 with M>1, support ZC sequence for overlaid sequence.

FFS details

Agreement

From RAN1 perspective, support X=11 PRBs for LP-WUS and LP-SS with SCS 60kHz and 120kHz for FR2.

Agreement

For the SCS used for LP-WUS and LP-SS, further discuss the following options:

· The single SCS is configured by gNB.

· The single SCS is determined by pre-defined rule.

R1-2409091 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Wednesday session

Agreement

In case of overlaid OFDM sequence not carrying information:

· Option 1: Single overlaid sequence is on each OOK ‘ON’ symbol.

· Note 1: multiple overlaid OFDM sequences are specified.

· Note 2: gNB can configure different overlaid OFDM sequence(s) for different cells.

R1-2409242 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday

Agreement

Regarding the maximum number of candidate overlaid sequences to carry LP-WUS information per OOK ON chip for one cell, down-select from the below:

· 4

· 8

· 16

· 32

· 64 for M not larger than 2.

· FFS whether the same or different set of candidate overlaid sequences are used for different cells.

R1-2409243 Summary #5 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Agreement

To determine the binary sequences for LP-SS, consider the following for performance comparison:

· Sync accuracy T’: the achieved sync accuracy T’ for a set of 4 sequences with the same number of occupied OFDM symbols (timing estimation error smaller than ≤T’ us for P=90 % of the time for SNR=-3dB, -6dB (low priority))

Assume the sliding window size is at least [-25us, 25us].

RRM measurement accuracy X: the achieved measurement accuracy within range ± XdB for Q=90% measurements based on Y LP-SS samples within a period comparable to Z=the length of I-DRX cycle that is larger or equal to 1.28s

Assume X= 3.5dB shall be satisfied for LP-RSRP and LP-RSRQ, based on Y=1, 4 and Z=1.28s for comparison

Cross correlation: maximum cross-cor value/ maximum auto-cor value

FFS how to use cross-correlation for comparison

Note: refer to RAN4 RRM assumption for the inter-cell interference

Agreement

Down-select among the following alternatives for LP-WUS information for OOK to meet target requirements:

adding CRC
channel coding other than Manchester coding, including rate matching if any
mapped to a binary sequence/codeword, include truncation if any
repetition, including rate matching if any
Note: combination of options above is not precluded
Note: combination of Manchester coding with above is assumed

FFS how LP-WUS is transmitted within a MO/Mos.

Agreement

Support overlaid OFDM sequence(s) for LP-SS:

LP-SS reuses the overlaid OFDM sequence(s) specified for LP-WUS. The design on overlaid OFDM sequence(s) specified for LP-WUS doesn’t target for sync and RRM measurement performance based on overlaid OFDM sequence for LP-SS.
Whether to transmit LP-SS by using a specified overlaid OFDM sequence is configurable.

Applicable at least for OOK-1 and FFS for OOK-4

From RAN1 perspective, it is not intended to introduce new RAN4 requirements specific to overlaid sequences

Reminder to companies who are interested in LP-SS:

Evaluation results on binary sequences for LP-SS are to be collected in RAN1 #119 meeting for comparison.

Final summary in R1-2409308.

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2407615 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2407635 Discussion on LP-WUS Operation in IDLE/INACTIVE modes TCL

R1-2407665 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2407715 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum Communications

R1-2407870 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2407914 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2407978 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2408056 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2408075 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE Corporation, Sanechips

R1-2408130 Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2408218 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2408254 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2408281 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2408345 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2408417 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2408477 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2408500 Discussion on LP-WUS operation in idle/inactive mode Fujitsu

R1-2408538 LP-WUS operation in IDLE/Inactive mode Nokia

R1-2408575 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2408592 On LR and MR operating frequencies Vodafone

R1-2408655 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2408680 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2408692 LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

R1-2408795 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2408821 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2408859 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2408917 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2408986 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2408479 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Monday session

Agreement

Confirm the following working assumption for iDRX: For each UE, the periodicity of LO is the same as its iDRX cycle.

Agreement

For the mapping between LO and PO, supports at least Option 1 (UEs monitoring the same PO monitor the same LO).

Agreement

From RAN1 perspective, when a UE is monitoring LP-WUS (based on the entry/exit condition for LP-WUS), a UE is not required to monitor a PO if

it does not detect a LP-WUS on the monitored LO,
or the LP-WUS does not indicate a wake-up indication for the UE’s corresponding subgroup.

R1-2408480 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement

For the offset value(s) between an LO and a reference PO/PF, consider the following options:

Definition: The gap between an LO and a PO is considered to be no less than the wake-up delay a UE supports if the gap between the end of the last LP-WUS MO the UE monitors in the LO and the start of the PO is no less than the wake-up delay.
Option 1: gNB configures a single offset value.

If the gap between an LO and the PO associated with the offset is no less than the wake-up delay a UE supports, the UE monitors the PO associated with the offset after receiving a wake-up indication in a LP-WUS.
Otherwise,

Option 1-1: the UE follows the legacy paging monitoring procedure.
Option 1-2: the UE monitors LP-WUS. If it receives a wake-up indication in a LP-WUS, it monitors the first PO after its reported wake-up delay.

Option 2: gNB configures one or multiple offset values.

For the same PO, each offset corresponds to a LO.

This does not preclude the possibility that the same LO may correspond to different POs with different offset values.

Option 2A: A UE does not expect that the gap between the LO associated with the largest offset and the corresponding PO is less than the wake-up delay the UE supports. The UE monitors the LO associated with one offset that has a gap between the LO and the corresponding PO no less than the wake-up delay.

This implies that the gNB needs to configure at least one offset value that is no less than the largest wake-up delay supported by the UEs.
FFS exactly how to choose the offset

Option 2B:

If the gap between the LO associated with the largest offset and the corresponding PO is no less than the wake-up delay a UE supports, the UE monitors the LO associated with one offset that has a gap between the LO and the PO associated with the offset no less than the wake-up delay.

FFS exactly how to choose the offset

Otherwise,

Option 2B-1: the UE follows the legacy paging monitoring procedure.
Option 2B-2: the UE monitors LP-WUS. If it receives a wake-up indication in a LP-WUS, it monitors the first PO after its reported wake-up delay.

FFS exactly how to choose the offset

FFS the UE shall monitor the LO associated with additional offset(s)

Note: The PO mentioned above refers to legacy PO configured for the UE.

Agreement

At least the following codepoints are supported for LP-WUS:

One codepoint corresponding to each of the subgroups that can be indicated by LP-WUS
One codepoint corresponding to all the subgroups that can be indicated by LP-WUS
FFS: Additional codepoints

Agreement

Support 3 candidate values for the wake-up delay capability a UE reports, two values for ultra-deep sleep state and one value for deep sleep state.

FFS the values
Note: Ultra-deep sleep state and deep sleep state are mentioned above solely for the purpose of RAN1 discussions and it is not intended to be captured in specifications from RAN1 perspective

R1-2408481 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

R1-2409239 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Agreement

Each LP-WUS is QCLed with one SSB. Each LP-SS is QCLed with one SSB.

FFS QCL Type A or Type C and/or Type D
FFS implicit QCL determination or some signaling is required

Agreement

The number of beams for LP-SS is the same as the number of beams for the LP-WUS MOs in an LO.

R1-2409240 Summary #5 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

Agreement

When K (K>1) LP-WUS MOs are configured for each beam in an LO, down select between

Option A: K LP-WUS MOs for a beam are divided into M (M >=1) groups of R LP-WUS MOs. A UE monitors all or some of the MO(s) within the K LP-WUS MOs.

For each group of R LP-WUS MOs, the same LP-WUS information is transmitted.

FFS how the same LP-WUS information is transmitted in the R LP-WUS MOs

Different LP-WUS information can be transmitted in different groups of R LP-WUS MOs.

M = 1 and M > 1 is supported.

FFS: detailed UE monitoring behavior

FFS R=1 or R>= 1

Option B: K LP-WUS MOs for a beam are divided into G (G >= 1) groups of R*M (M >= 1) LP-WUS MOs. A UE monitors all or some of the MO(s) within one group of R*M LP-WUS MOs based on its subgroup ID.

Each group of R*M LP-WUS MOs is further divided into M groups of R LP-WUS MOs.

For each group of R LP-WUS MOs, the same LP-WUS information is transmitted.

FFS how the same LP-WUS information is transmitted in the R LP-WUS MOs

Different LP-WUS information can be transmitted in different groups of R LP-WUS MOs.
FFS: detailed UE monitoring behavior

M = 1 and M > 1 is supported.

FFS R=1 or R>=1

Note: this achieves the same purpose as “Option 3: UEs monitoring the same PO are divided into multiple sets of subgroups, with UEs within each set of subgroups monitoring the same LO.”

Working Assumption

The maximum number of subgroups per PO supported in Rel-19 is 32.

Final summary in R1-2409241.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2407666 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2407716 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum Communications

R1-2407871 Discussion on LP-WUS operation in CONNECTED modes vivo

R1-2407915 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2407979 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2408057 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2408076 Discussion on LP-WUS operation in CONNECTED mode ZTE Corporation, Sanechips

R1-2408131 Further consideration on LP-WUS operation in connected mode OPPO

R1-2408219 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2408255 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2408282 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2408322 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2408418 LP-WUS operation in CONNECTED mode Sony

R1-2408478 LP-WUS operation in CONNECTED modes Apple

R1-2408495 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2408539 LP-WUS operation in CONNECTED mode Nokia

R1-2408576 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2408656 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2408681 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2408693 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2408796 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2408822 LP-WUS operation in CONNECTED mode Ericsson

R1-2408860 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2408921 Discussion on LP-WUS procedures in Connected mode TCL

R1-2409010 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Monday session

Agreement

For Option 1-1 of LP-WUS CONNECTED mode operation, the followings are assumed from RAN1 perspective.

LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer
UE is configured with legacy C-DRX configurations as Rel-18
UE behaviors related to CDRX active time triggered by all legacy DRX timers are not affected unless included in this proposal
No impact on RRM/RLM/BFD measurement requirements is assumed
For periodic CSI/L1-RSRP reporting, UE can be configured with one of the following (same as Rel-16 DCP)

Periodic CSI/L1-RSRP is not reported during the time given by the configured drx-onDurationTimer if UE is not indicated to wake-up
Periodic CSI/L1-RSRP is periodically reported during the time given by the configured drx-onDurationTimer regardless if UE is indicated to wake-up or not

Note: Periodic CSI/L1-RSRP is reported during CDRX active time as in legacy specification

Agreement

Confirm following working assumption

Working Assumption

From RAN1 perspective, for RRC CONNECTED mode, PDCCH monitoring is triggered by LP-WUS with C-DRX configuration

· Support Option 1-1: LP-WUS monitoring according to the LP-WUS monitoring configuration before drx-onDurationTimer to trigger the starting of the drx-onDurationTimer.

· Support Option 1-2: LP-WUS monitoring outside at least legacy C-DRX active time according to the LP-WUS monitoring configuration to trigger PDCCH monitoring.

· FFS whether/how to support both Option 1-1 and Option 1-2 simultaneously configured for the same UE

Note: Above can be revisited considering RAN2 decisions.

R1-2409197 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Wednesday session

Agreement

For RRC CONNECTED mode, UE reports one value for each SCS from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting.

· FFS: X

· FFS: definition of reported candidate value

· UE can indicate its preference for configured time offset between LP-WUS and PDCCH reception using UAI mechanism. FFS details. UAI is optional.

· FFS: A single time offset is configured for a UE at a given time.

R1-2409237 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

LP-WUS is supported when UE is configured with NR-DC in RRC CONNECTED mode

· Above is supported for the case PDCCH monitoring is triggered by LP-WUS in the same cell group

· FFS: The cell(s) where PDCCH monitoring triggered by a LP-WUS is applicable

R1-2409265 FL summary #4 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

For LP-WUS CONNECTED mode operation, Option 1-2 can be configured separately from Option 1-1

· FFS whether/how to support both Option 1-1 and Option 1-2 simultaneously configured for the same UE

Agreement

Regarding the potential restriction for LP-WUS configuration in relation with C-DRX configuration for option 1-2 of LP-WUS CONNECTED mode operation, from RAN1 perspective,

· Opt2: At least LP-WUS periodicity is no larger than long C-DRX cycle, FFS other restrictions

· Introducing monitoring window is not precluded

Final summary in R1-2409266.

RAN1#119

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-241824 for detailed scope of the WI.

[119-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2410885 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

For information, not treated.

9.6.1 LP-WUS and LP-SS design

R1-2409423 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2409444 LP-WUS and LP-SS design Nokia

R1-2409456 Discussion on LP-WUS and LP-SS design for low power WUS InterDigital, Inc.

R1-2409476 Discussion on LP-WUS and LP-SS Design TCL

R1-2409520 Discussion on LP-WUS and LP-SS design CMCC

R1-2409534 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2409546 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2409559 Discussion on LP-WUS design ZTE Corporation, Sanechips

R1-2409605 Discussion on LP-WUS and LP-SS design Samsung

R1-2409644 Discussion on LP-WUS and LP-SS design Spreadtrum, UNISOC

R1-2409689 Discussion on LP-WUS and LP-SS design vivo

R1-2409811 LP-WUS and LP-SS design Apple

R1-2409860 Discussion on LP-WUS and LP-SS design NEC

R1-2409904 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2409949 Design of LP-WUS and LP-SS CATT

R1-2410036 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2410646 Signal design for LP-WUS and LP-SS OPPO (rev of R1-2410071)

R1-2410135 Discussion on LP-WUS and LP-SS design Fujitsu

R1-2410181 Discussion on LP-WUS and LP-SS design HONOR

R1-2410231 LP-WUS and LP-SS design Sony

R1-2410294 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2410310 LP-SS Code Sets and Comparison Everactive

R1-2410397 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2410419 Discussion on LP-WUS and LP-SS design Sharp

R1-2410444 LP-WUS and LP-SS design Ericsson

R1-2410486 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2410510 LP-WUS and LP-SS design MediaTek Inc.

R1-2410556 Discussion on LP-WUS and LP-SS design Lenovo

R1-2410569 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2410747 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Monday session

Agreement

Update the existing agreement as below

In case of overlaid OFDM sequence carrying information, support option 2:

o ~~Option 2-1: The overlaid OFDM sequence(s) carry part of information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by OFDM sequence(s) and location of the OFDM sequence(s)/OOK~~ ~~‘ON’~~ ~~symbols.~~

o Option 2-2: The overlaid OFDM sequence(s) carry all information bits of LP-WUS. OFDM-based LP-WUR can obtain the whole information bits by the overlaid OFDM sequence(s)

§ FFS the how the information bits are carried by the overlaid OFDM sequence(s)

Note: the overlaid OFDM sequence in each OOK ‘ON’ symbol can be different according to information bits to be carried by the overlaid OFDM sequence within the LP-WUS.

R1-2410748 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

For the overlaid OFDM sequence in time domain, the sequence is generated based on

· M=1, is given by the largest prime number such that,is the overlaid OFDM sequence length.

o The base overlaid sequence is generated by extension of

o With CS(s) applied to the base overlaid OFDM sequence if any:denotes the potential cyclic shift (s)

· M=2, 4, is down-selected from the following:

o Alt1: is given by the largest prime number such that,is the overlaid OFDM sequence length.

§ The base overlaid sequenceis generated by extension of

§ With CS(s) applied to the base overlaid OFDM sequence if any:denotes the potential cyclic shift (s)

§ Note it doesn’t preclude any pulse shaping scheme if any.

o Alt2:is given by the largest prime number such that, is the overlaid OFDM sequence length.

§ The base overlaid sequenceis generated by inserting zeros before and/or after . The total number of zeros is.

For example,,

§ With CS(s) applied to the base overlaid OFDM sequence if any: denotes the potential cyclic shift (s)

For example,,

where,

§ FFS the value of G, with G>0.

· FFS value(s) of root q and/or CS for generating the candidate sequences if applied

· FFS on whether changes are needed to handle intra-/inter-cell interference

· Note: the overlaid OFDM sequence in time domain is based on potential modification to ZC sequence as listed above.

o Above overrides any previous RAN1 agreement / working assumption

Agreement

At least for M>1, for the overlaid OFDM sequence in time domain, down-select the sequence length from the following:

· Alt1:, with

o FFS how to map the generated overlaid OFDM sequence to the frequency domain

· Alt2:

· Note: X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included)

Agreement

CS(s) and/or root(s) used for overlaid OFDM sequence in the time domain are derived from RRC signalling:

· FFS: the set of values of CS and root for configuration

· FFS: details of the RRC signaling

Agreement

For the length L of LP-SS binary sequence, limit the selection to the following:

M=1, L= {4, 6, 8}
M=2, L= {8, 12, 16}
M=4, L= {16, 32}

Agreement

To compare LP-SS binary sequence performance, cross-correlation is deprioritized over sync accuracy, i.e., cross-correlation within a set of 4 sequences is further compared for different sets of sequences with similar sync accuracy.

R1-2410837 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Wednesday session

Agreement

For the M value for LP-WUS and LP-SS, down-select one alternative from the following in RAN1#120:

· Alt1: The M values for LP-WUS and LP-SS are always same.

· Alt2: The M values for LP-WUS and LP-SS can be configured to be same or different. M value for LP-WUS cannot be larger than that of LP-SS.

· Alt3: The M values for LP-WUS and LP-SS can be configured to be same or different.

R1-2410838 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday session

Agreement

Regarding the maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell:

· support maximum 4 candidates overlaid sequences for M=4

For future meetings:

Companies are encouraged to consider [H][FL4] Proposal 3.3-1 in R1-2410838.

Agreement

Regarding whether to support additional sync signal to LP-SS, down-selection from the following:

· Option 1A: No additional sync signal, LP-SS periodicity =320ms

o Additionally support at least one of [80ms,160ms]

§ FFS: whether different values can be applicable for different M values

· Option 1B: No additional sync signal, LP-SS periodicity =320ms

o No additional support of other periodicities

Option 2: With additional sync signal, LP-SS periodicity =320ms

o FFS additionally support other LP-SS periodicities

o FFS details on additional sync signal

o FFS additional sync signal is configurable and/or conditionally present

R1-2410883 Summary #5 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

For future meetings:

Companies are encouraged to consider the following for future discussions

Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs,

Option 1: A bitmap with each bit corresponding to [one or more] UEs

o 1A No CRC

§ Per bit coding, e.g., one bit is mapped to one of 2 codeword/sequences

§ The maximum number of codewords targeting per bit position in the bitmap for a UE is 1

§ FFS coded bit length

§ Single MO

o 1B No CRC

§ Bitmap-level coding, e.g., one bitmap of L bits is mapped to one of 2^L codeword/sequences

§ The maximum number of codewords/sequences targeting for a UE is 2^L-1

§ Single MO

o 1C With CRC

§ FFS CRC length

§ Single MO

Option 2: A codepoint value corresponding to [one or more] UEs

o 2A only 1-1 mapping from codepoint to UE

§ The maximum number of codepoints targeting per MO for a UE is 1

§ FFS the maximum number of MOs to be detected by a UE

o 2B 1-to-1, 1-to-all mapping from codepoint to UEs

§ The maximum number of codepoints targeting per MO for a UE is up to 2

§ FFS the maximum number of MOs to be detected by a UE

o 2C 1-to-X mapping from codepoint to UEs,

§ The maximum number of codepoints targeting per MO for a UE is up to

§ FFS the maximum number of MOs to be detected by a UE

Note: L is the number of UEs associated monitoring the same WUS

Agreement

For RRC idle/inactive state, for the case where associated CD-SSB and initial DL BWP have the same SCS at least when the associated CD-SSB and LP-WUS are on the same carrier

· The single SCS for LP-WUS/LP-SS is same as the associated CD-SSB

· FFS: Case where associated CD-SSB and initial DL BWP have different SCSs

· FFS: Which initial BWP for RedCap

R1-2410925 Template for collecting LP-SS binary sequence results Moderator (vivo)

Agreement

For collecting LP-SS binary sequence results

Endorse the template for collecting LP-SS binary sequence results in R1-2410925
Email discussion for collecting LP-SS binary sequences by 10th Jan.
Please include your cross-checking results (e.g., a separate excel sheet) in the t-doc for #120.

R1-2410884 Final summary of discussions on LP-WUS and LP-SS design Moderator (vivo)

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2409424 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2409445 LP-WUS operation in IDLE/Inactive mode Nokia

R1-2409457 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2409477 Discussion on LP-WUS Operation in IDLE/INACTIVE modes TCL

R1-2409521 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2409547 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2409560 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE Corporation, Sanechips

R1-2409606 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2409645 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum, UNISOC

R1-2409690 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2409812 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2409861 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2409905 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2409950 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2410037 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2410072 Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2410232 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2410274 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2410295 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2410300 On LR and MR operating frequencies Vodafone, Deutsche Telekom

R1-2410398 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2410420 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2410445 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2410487 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2410511 LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

R1-2410557 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2410568 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2409814 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Monday session

Agreement

Confirm the following working assumption with the addition of the note at the bottom:

Working Assumption

From RAN1 perspective, for the entry/exit conditions for LP-WUS monitoring in IDLE/inactive mode,

· The UE may start LP-WUS monitoring if

o the serving cell measurement performed by the MR is above entry threshold(s), if configured by the gNB

o FFS other conditions, and if any, whether all or one or some of the conditions need to be satisfied

· If UE starts LP-WUS monitoring, it may stop the legacy PO monitoring before UE receives LP-WUS indicating wake-up

· The UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if

o the serving cell measurement performed by the LR is below exit threshold(s), if configured by the gNB

o FFS other conditions, and if any, whether all or one or some of the conditions need to be satisfied

· FFS the serving cell measurement metrics

· The entry/exit thresholds can be configured separately for different types of LR

· It is left to RAN2 discussion whether the threshold(s) are always configured by the gNB.

· Note: This may be revisited based on the RAN2/RAN4 discussion.

Note: this does not intend to impact any agreements and working assumptions made in RAN1/RAN2 after the working assumption.

Agreement

At least support the case that the number of beams for LP-WUS/LP-SS is the same as the number of SSB beams.

Conclusion

Do not support one-to-multiple mapping between the LP-WUS/LP-SS beams and the SSB beams.

Conclusion

No additional RAN1 specification impact specific to support multiple-to-one mapping between the LP-WUS/LP-SS beams and the SSB beams.

R1-2409815 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement

For the offset value(s) between an LO and a reference PO/PF, down-select between

Option 1-1
Configurability between Option 1-1 and Option 1-2
Option 2B-1

Agreement

At least for the 1:1 LO to PO mapping,

The maximum value of M for Option A or Option B with G=1 (if either of them is supported) is 4.

Conclusion

There is no RAN1 consensus to support additional codepoints indicating wake-up at least for 1:1 LO to PO mapping.

R1-2409816 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Wednesday session

For future meetings:

Consider the following alternatives for UE capability report on the wake-up delay:

Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[80ms], [500ms] and [900ms]}.

The reported values assume SSB periodicity of 20ms, where [80ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization.
FFS: translation of wake-up delay for different SSB periodicities

Alt 2: For the wake-up delay capability report, UE reports a pair of values for main radio ramp up and the number of SSBs needed for synchronization (D, NSSB). Support the following 3 candidate capabilities: {[(20ms, 3), (400ms, 5), (800ms, 5)]}.
Alt 3: Modify the previous agreement on UE capability report on the wake-up delay to UE capability report on the main radio ramp up time. The number of SSBs needed for synchronization is defined in specs, and different number of SSBs can be defined for different UE capability on the main radio ramp up time.

3 candidate values for the main radio ramp up time: {[20ms, 400ms, 800ms]}
The number of SSBs needed for synchronization is defined as [3, 5, 5] for [20ms, 400ms, 800ms] main radio ramp up time, respectively.

Alt 4: Modify the previous agreement on UE capability report on the wake-up delay to UE capability report on the main radio ramp up time. The time needed for synchronization will be defined by RAN4 requirements later.

Agreement

Each LP-WUS or LP-SS is QCLed with an SSB with [select one from ‘typeA’, ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

R1-2410861 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Working Assumption

If LP-WUS design support 32 subgroups within one MO, do not support Option 3 for LO to PO mapping or Option B for MO configuration.

Conclusion

From RAN1 perspective, there is no consensus on the following proposal:

UE monitors the legacy PO (and may monitor PEI) and may stop LP-WUS monitoring if the UE has not received LP-WUS for a long time.

R1-2410862 Summary #5 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

For future meetings:

Companies are encouraged to consider section 3.5 of R1-2410862 for further discussions in future meetings.

Final summary in R1-2410863.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2409425 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2409446 LP-WUS operation in CONNECTED mode Nokia

R1-2409458 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2409522 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2409561 Discussion on LP-WUS operation in CONNECTED mode ZTE Corporation, Sanechips

R1-2409607 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2409646 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum, UNISOC

R1-2409691 Discussion on LP-WUS operation in CONNECTED modes vivo

R1-2409813 LP-WUS operation in CONNECTED modes Apple

R1-2409862 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2409875 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2409906 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2409951 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2410073 Further consideration on LP-WUS operation in connected mode OPPO

R1-2410233 LP-WUS operation in CONNECTED mode Sony

R1-2410275 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2410296 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2410358 Discussion on LP-WUS procedures in Connected mode TCL

R1-2410363 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2410399 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2410421 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2410446 LP-WUS operation in CONNECTED mode Ericsson

R1-2410488 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2410512 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2410699 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Monday session

Agreement

For LP-WUS monitoring in RRC CONNECTED mode, SSB and/or CSI-RS can be the QCL source of LP-WUS QCL type(s) is {Type A or Type C – for down-selection} and Type D, when applicable.

Agreement

LP-WUS in RRC CONNECTED mode does not include Scell dormancy indication.

· Note: LP-WUS indication does not impact SCell dormancy behavior.

R1-2410804 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Wednesday session

Agreement

For LP-WUS CONNECTED mode operation, the following case is not supported:

· Both Option 1-1 and Option 1-2 are simultaneously configured for the same UE in a given cell.

R1-2410859 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

For LP-WUS MOs in connected mode for Option 1-1, following is considered further discussion and possible down-selection

Approach 1:

LP-WUS MOs, including periodicity and offset, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
UE selectively monitors LP-WUS in the LP-WUS MOs identified by other parameters such as time offset prior to the start of drx-onDurationTimer.

Approach 2:

LP-WUS MOs, including periodicity and offset, are identified based on the slot that drx-onDurationTimer would start and a new RRC parameter indicating the time offset until the slot that drx-onDurationTimer would start.

FFS: An RRC parameter indicates the duration where the UE monitors LP-WUS [consecutively in time]

FFS: the consecutive LP-WUS MOs in time identified by the RRC parameter are associated with a same C-DRX cycle;
FFS: LP-WUS MOs in time identified by the RRC parameter provides consistent indication for the same C-DRX cycle of the UE, i.e., UE does not expect to detect more than one LP-WUSs with different indications for the UE in the LP-WUS MOs associated with the same C-DRX cycle.

For LP-WUS MOs in connected mode for Option 1-2, following is considered further

Approach 1:

LP-WUS MOs, including periodicity and offset, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
UE monitors LP-WUS in the LP-WUS MOs and starts a new timer for PDCCH monitoring triggered by LP-WUS, after a time offset.

Approach 2:

Periodicity/offset of the slot that the new timer for PDCCH monitoring may be potentially triggered by LP-WUS are configured by RRC parameters.
LP-WUS MOs, including periodicity and offset, are identified based on the slot that new timer would start and a new RRC parameter indicating the time offset until the slot that new timer would start.

FFS: An RRC parameter indicates the duration where the UE monitors LP-WUS [consecutively in time]

FFS: the consecutive LP-WUS MOs in time identified by the RRC parameter are associated with the same slot that the new timer would start;
FFS: LP-WUS MOs in time identified by the RRC parameter provides consistent indication for the same slot that the new timer would start, i.e., UE does not expect to detect more than one LP-WUSs with different indications for the UE in the LP-WUS MOs associated with the same slot that the new timer would start.

R1-2410906 FL summary #4 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

For Option 1-2 of LP-WUS CONNECTED mode operation, for explicit indication to stop the new timer for PDCCH monitoring in Option 1-2 and drx-InactivityTimer for the DRX group, RAN1 identified the following potential solution

Use existing DRX Command MAC CE and Long DRX Command MAC CE
When UE is not in C-DRX active time, UE monitors LP-WUS

Send LS to RAN2 to ask the feasibility of the above potential solution.

Conclusion

For Option 1-1 of LP-WUS CONNECTED mode operation, RAN1 assumes existing DRX Command MAC CE and Long DRX Command MAC CE can be used to stop drx-onDurationTimer and~~/or~~ drx-InactivityTimer for the DRX group

- When UE is not in C-DRX active time, UE monitors LP-WUS

Send LS to RAN2 to ask whether RAN2 has same understanding or not.

R1-2410908 Draft LS on LP-WUS operation in CONNECTED modes Moderator (NTT DOCOMO)

Decision: The draft LS is endorsed. Final LS on LP-WUS operation in CONNECTED mode is approved in R1-2410909.

Agreement

For Option 1-2, for LP-WUS CONNECTED mode operation, the periodic CSI/L1-RSRP reporting operation is same as Rel-16 DCP, that is the UE can be configured with a parameter to enable/disable periodic CSI/L1-RSRP reporting, respectively:

If the parameter is NOT configured:

If the UE is not indicated to wake up by LP-WUS, the periodic CSI/L1-RSRP is not reported.
If the UE is indicated to wake up by LP-WUS, the periodic CSI/L1-RSRP is reported during the DRX active time.

If the parameter is configured:

If the UE is not indicated to wake up by LP-WUS, the periodic CSI/L1-RSRP is reported during the time given by the configured drx-onDurationTimer in DRX-Config for the case when UE is outside C-DRX active time.
If the UE is indicated to wake up by LP-WUS, the periodic CSI/L1-RSRP is reported during the DRX active time.

FFS: Whether RAN1 spec impact is required.

For future meetings:

Companies are encouraged to consider [Fri]Combined Proposal 3.2-1/3.2-2c of R1-2410906 for further discussions in future meetings.

Final summary in R1-2410907.

RAN1#120

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-241824 for detailed scope of the WI. Additional RAN guidance on Rel-19 LP-WUS/WUR can be found in RP-243266.

Rapporteur to provide initial input on higher layer signalling under agenda item 9.6. For input on higher layer signalling from any other source, please include it as part of your tdoc to relevant sub-agenda items.

[120-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2500356 Rapporteur input on RRC parameters for Rel-19 LP-WUS/WUR vivo, DOCOMO

R1-2501630 Summary of discussion on RRC parameters for Rel-19 LP-WUS/WUR vivo (WI rapporteur)

R1-2501585 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

9.6.1 LP-WUS and LP-SS design

R1-2500048 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2500063 Discussion on LP-WUS and LP-SS Design TCL

R1-2500073 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2500131 Discussion on LP-WUS design ZTE Corporation, Sanechips

R1-2500176 Discussion on LP-WUS and LP-SS design Spreadtrum, UNISOC

R1-2500231 Design of LP-WUS and LP-SS CATT

R1-2500294 Discussion on LP-WUS and LP-SS design CMCC

R1-2500357 Discussion on LP-WUS and LP-SS design vivo

R1-2501364 Signal design for LP-WUS and LP-SS OPPO (rev of R1-2500437)

R1-2500491 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2500496 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2500530 Discussion on LP-WUS and LP-SS design InterDigital, Inc.

R1-2500573 LP-WUS and LP-SS design Nokia

R1-2500602 Discussion on LP-WUS and LP-SS design NEC

R1-2500656 LP-WUS and LP-SS design Sony

R1-2500739 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2500788 LP-WUS and LP-SS design Apple

R1-2500857 Discussion on LP-WUS and LP-SS design Samsung

R1-2500956 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2501023 LP-WUS and LP-SS design MediaTek Inc.

R1-2501096 Discussion on LP-WUS and LP-SS design Sharp

R1-2501100 Discussion on LP-WUS and LP-SS design Lenovo

R1-2501113 Discussion on LP-WUS and LP-SS design HONOR

R1-2501163 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2501209 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2501254 LP-WUS and LP-SS design Ericsson

R1-2501294 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2501424 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Monday session

Agreement

For LP-WUS information carried by OOK, select alt 1 for codepoint to meet FAR and MDR performance.

Alt 1: Coding with rate matching if any

For more than 2 information bits: RM coding as in section 5.3.3.3 of 38.212 (FFS: whether scrambling in the same section is applied or not)
2 information bits (if supported): coding as in section 5.3.3.2 of 38.212 (FFS: whether scrambling in the same section is applied or not)
1 information bit (if supported): repetition as in section 5.3.3.1 of 38.212 (FFS: whether scrambling in the same section is applied or not)
FFS: Code block length
FFS: Further repetition before or after Manchester coding

Conclusion

For RRC idle/inactive, LP-WUS is not supported for the case where associated CD-SSB and initial DL BWP have different SCS.

R1-2501425 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

At least for M>1, for the overlaid OFDM sequence length, support

· Alt2:

· Note: X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included)

Agreement

Update the agreements in RAN1 #118bis as below

Agreement

Support overlaid OFDM sequence(s) for LP-SS:

- LP-SS reuses the overlaid OFDM sequence(s) specified for LP-WUS. The design on overlaid OFDM sequence(s) specified for LP-WUS doesn’t target for sync and RRM measurement performance based on overlaid OFDM sequence for LP-SS.

o Applicable to both OOK-1 and OOK-4

- Whether to transmit LP-SS by using a specified overlaid OFDM sequence is configurable.

o Applicable ~~at least~~ for OOK-1 only ~~and FFS for OOK-4~~

- From RAN1 perspective, it is not intended to introduce new RAN4 requirements specific to overlaid sequences

Agreement

For RRC connected, for LP-WUS SCS:

· Alt 1: LP-WUS SCS is same as the active DL BWP

R1-2501519 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Wednesday session

Working Assumption

Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs,

· codepoint based

o The maximum number of codepoints checked per MO by a UE is up to 8

§ Depending on UE capability, a UE may support less than 8

R1-2501520 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday session

Agreement

For M=2, 4, is given by the largest prime number such that,is the overlaid OFDM sequence length.

· The base overlaid sequenceis generated by extension of

· With CS(s) applied to the base overlaid OFDM sequence if any:denotes the potential cyclic shift (s)

· Note it doesn’t preclude any pulse shaping scheme if any.

Agreement

For RRC connected, LP-WUS frequency resource can be outside of active DL BWP but has to be within the same carrier as the active DL BWP

· Basic capability is LP-WUS, if present, frequency resource within active DL BWP. LP-WUS frequency resource outside of active DL BWP is subject to separate UE capability

· No RAN1 optimization specific to the case where LP-WUS frequency resource is outside of active DL BWP

R1-2501583 Summary #5 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Agreement

For M=1, L=4 (if supported), the set of LP-SS binary sequences is:

[0 1 0 1]

[0 1 1 0]

[1 0 0 1]

[1 0 1 0]

Agreement

For M=1, L=6 (if supported), the set of LP-SS sequence is:

[1 0 1 0 1 0]

[0 1 0 1 0 1]

[1 0 0 1 0 1]

[1 0 1 0 0 1]

Agreement

For M=1, L=8 (if supported), the set of LP-SS sequence is:

[1 0 1 0 0 1 0 1]

[1 0 1 0 1 0 0 1]

[1 0 0 1 0 1 0 1]

[0 1 0 1 0 1 0 1]

Agreement

For M=2, L=8 (if supported), the set of LP-SS sequence is:

[0 1 0 1 1 0 0 1]

[0 1 1 0 0 1 0 1]

[0 1 1 0 1 0 0 1]

[1 0 0 1 0 1 1 0]

Agreement

For M=2, L=12 (if supported), the set of LP-SS sequence is:

[1 0 0 1 1 0 0 1 1 0 0 1]

[0 1 1 0 1 0 0 1 1 0 0 1]

[0 1 1 0 0 1 1 0 1 0 0 1]

[0 1 1 0 0 1 0 1 1 0 0 1]

Agreement

For M=2, L=16 (if supported), the set of LP-SS sequence is:

[1 0 0 1 0 1 0 1 1 0 0 1 1 0 0 1]

[1 0 0 1 1 0 0 1 0 1 1 0 0 1 0 1]

[1 0 0 1 1 0 1 0 0 1 0 1 1 0 0 1]

[1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1]

Agreement

For M=4, L=16 (if supported), the set of LP-SS sequence is down-selected between:

· Set 1

[0 1 1 0 1 0 0 1 1 0 1 0 1 0 1 0]

[0 1 1 0 1 0 1 0 1 0 0 1 1 0 1 0]

[1 0 1 0 0 1 1 0 1 0 1 0 1 0 0 1]

[1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0]

· Set 2

[1 0 0 0 1 0 0 0 0 0 0 1 0 0 1 0]

[1 0 0 0 0 1 0 0 1 0 0 0 0 0 1 0]

[1 0 0 0 0 1 0 0 0 1 0 0 1 0 0 0]

[1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1]

Agreement

For M=4, L=32(if supported), the set of LP-SS sequence is down-selected between:

· Set 1:

[0 1 0 1 1 0 1 0 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1]

[0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 1 1 0 0 1 1 0 1 0 1 0 1 0 0 1 0 1]

[0 1 0 1 0 1 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0]

[0 1 0 1 0 1 1 0 0 1 0 1 1 0 1 0 0 1 1 0 0 1 1 0 1 0 1 0 0 1 0 1]

· Set 2

[0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 1 0 1 0 0]

[0 0 0 1 0 1 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 0 1 0 1 0 0]

[0 0 1 0 0 0 1 0 1 0 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 0 1 0 0 0 1 0]

[0 0 1 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 1 0 1 0 0 0 0 1 0 0 0 0 1 0]

Agreement

For idle mode, regarding the maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell:

· support maximum 16 candidates overlaid sequences for M=1

· support maximum 8 candidates overlaid sequences for M=2

· For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value.

o FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.

Agreement

For WUS information carried by the overlaid OFDM sequence(s), consider at least the following alternatives:

Alt 1: Raw information bits are mapped to sequence(s)
Alt 2: Raw information bits are mapped to sequence(s) after channel coding

o Same channel coding scheme(s) as OOK is applied.

§ FFS same or different rate matching and/or repetition factor as OOK

Alt 3: Codepoint/Subgroup is mapped to sequence(s)

R1-2501584 Final summary of discussions on LP-WUS and LP-SS design Moderator (vivo)

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2500049 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2500064 Discussion on LP-WUS Operation in IDLE/INACTIVE state TCL

R1-2500074 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2500132 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE Corporation, Sanechips

R1-2500177 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum, UNISOC

R1-2500232 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2500295 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2500358 Discussion on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2500438 Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2500492 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2500531 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2500574 LP-WUS operation in IDLE/Inactive mode Nokia

R1-2500603 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2500657 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2500740 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2500789 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2500858 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2500916 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2500957 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2501024 LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

R1-2501097 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2501101 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2501164 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2501210 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2501255 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2501293 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2500791 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Monday session

Agreement

The EPRE ratio between LP-WUS/LP-SS and SSB can be configured by the gNB.

FFS whether there is a common configuration or separate configuration for LP-WUS and LP-SS
Above is not applicable for the case when all the subcarriers for LP-WUS/LP-SS are transmitted with zero power (from baseband perspective)
Above does not mandate any UE implementation for different receiver types
FFS: whether/how to support for the case when there are different number of OOK ON symbols in different OFDM symbols (if supported)

Agreement

For the offset value(s) between an LO and a reference PO/PF, at least a frame-level offset is provided.

· The reference point (reference PO/PF) for the frame-level offset is the start of the PF, or the first PF of the PF(s) (if mapping of POs from multiple PFs to one LO is supported), associated with the LO.

· FFS other offset value(s) to determine the MOs of the LO

Agreement

The previous agreement in RAN1#119 is updated as follows:

· Each LP-WUS or LP-SS is QCLed with an SSB with ~~[select one from ‘typeA’,~~ ‘typeC’], and when applicable, ‘typeD’ with the same SSB.

Agreement

Confirm the following working assumption with the additional text in red:

Working Assumption

From RAN1 perspective, for the RRM measurement metrics based on SSS for OFDM-based LP-WUR, use the same definition of SS-RSRP and SS-RSRQ for LP-SSS-RSRP and LP-SSS-RSRQ, respectively.

· Above is applicable for both time-domain processing or frequency-domain processing

· Above does not imply that RAN1 will introduce LP-SSS-RSRP and LP-SSS-RSRQ in the specifications

Existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

· The metrics SS-RSRP and SS-RSRQ are applicable for OFDM-based LP-WUR for RRC_IDLE and RRC_INACTIVE serving cell measurement.

· FFS: whether to remove or modify the restriction of using SMTC window for LP-SSS-RSRP/RSSI measurement.

R1-2500792 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement

For the LO to PO mapping from network perspective, support Option 2 (UEs corresponding to different POs monitor the same LO).

This should not increase the maximum number of codepoints per LO/LP-WUS compared to Option 1.
FFS conditions/restrictions for mapping multiple POs to one LO
Down-select between 2 and 4 for max number of POs per LO.

R1-2500793 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Wednesday session

Agreement

For UE capability report on the wake-up delay:

Alt 1: For the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}.

The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization.
FFS: translation of wake-up delay for different SSB periodicities
FFS: different sets of 3 candidate value for different SSB periodicities

Send an LS to RAN4 after the down-selection to confirm the number of SSBs

Agreement

For the offset value(s) between an LO and a reference PO/PF, adopt Option 2B-1.

· gNB can configure 1 or 2 offset values.

o FFS whether gNB can configure 3 offset values

· If multiple offset values are configured and if the gap between the LO associated with the largest offset value and the corresponding PO is no less than the wake-up delay a UE reports, the UE monitors the LO associated with the smallest offset value that has a gap between the LO and the PO no less than the wake-up delay.

o Note: if a single offset value is configured, UE behaviour is according to Option 1-1.

· All the UEs supporting LP-WUS for idle/inactive mode supports the configuration of 2 offset values (FFS: 3 values).

R1-2500794 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Agreement

Confirm the following working assumption with the modification:

Working Assumption

The maximum number of subgroups per PO supported in Rel-19 is 31 32.

From Friday session

R1-2501615 Draft LS on the wake-up delay for LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Decision: The draft LS is endorsed. Final LS is approved in R1-2501624.

Final summary in R1-2500795.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2500075 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2500133 Discussion on LP-WUS operation in CONNECTED mode ZTE Corporation, Sanechips

R1-2500178 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum, UNISOC

R1-2500233 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2500296 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2500359 Discussion on LP-WUS operation in CONNECTED modes vivo

R1-2500439 Further consideration on LP-WUS operation in connected mode OPPO

R1-2500505 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2500532 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2500575 LP-WUS operation in CONNECTED mode Nokia

R1-2500604 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2500658 LP-WUS operation in CONNECTED mode Sony

R1-2500741 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2500790 LP-WUS operation in CONNECTED modes Apple

R1-2500859 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2500886 Discussion on LP-WUS operation in CONNECTED modes Lenovo

R1-2500917 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2500958 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2501025 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2501098 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2501165 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2501211 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2501256 LP-WUS operation in CONNECTED mode Ericsson

R1-2501296 Discussion on LP-WUS procedures in Connected mode TCL

R1-2501420 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Monday session

Agreement

For RRC connected mode, UE does not monitor LP-WUS during C-DRX active time.

· FFS FAR and MDR impact.

Agreement

LP-WUS can be configured with legacy PDCCH skipping.

· Note: There is no intention to modify legacy PDCCH skipping.

Agreement

For RRC CONNECTED mode, LP-WUS can be configured with Rel-17 SSSG switching.

R1-2501487 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Tuesday session

Agreement

For the case when UE is configured with CA without dual DRX groups in RRC CONNECTED mode,

LP-WUS can be configured on a serving cell
LP-WUS indication is applicable to all serving cells

Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation

FFS: Whether the serving cell on which the LP-WUS is configured is only PCell or can be RRC configured cell other than PCell.

Agreement

For the case when UE is configured with NR-DC with CA without dual DRX groups or without CA in RRC CONNECTED mode,

LP-WUS can be configured on a serving cell per cell-group

This does not imply that LP-WUS has to be configured on both cell groups

LP-WUS indication is applicable to all serving cells in the cell-group

Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation

FFS whether to support this case as separate UE capability from CA case
FFS UE capability for monitoring LP-WUS on one cell group or both cell groups

FFS: Whether the serving cell on which the LP-WUS is configured is only PCell/PSCell or can be RRC configured cell other than Pcell/PSCell.

R1-2501535 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Wednesday session

Agreement

For RRC CONNECTED mode, LP-WUS can be configured with Cell DTX.

· FFS During Cell DTX inactive time, whether the UE is expected to monitor LP-WUS or not.

Conclusion

From RAN1 perspective, when LP-WUS monitoring is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers MR PDCCH monitoring according to the legacy UE behaviour.

Above applies at least for Option 1-1.

Agreement

For LP-WUS monitoring in RRC CONNECTED mode, select one of the options on how to define/configure/indicate QCL source of LP-WUS

Opt1: Separate indication/configuration for QCL source of LP-WUS
Opt2: Association of QCL source between LP-WUS and PDCCH/CORESET

R1-2501561 FL summary #4 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:

LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).
Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start

UE monitors the first Z LP-WUS MO(s) at or after Time offset2.

FFS: How to determine the value of Z

Time offset2 is RRC configured

UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. FFS: How X is determined.

R1-2501586 FL summary #5 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:

LP-WUS MOs, including periodicity and time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).

FFS one or multiple MOs per periodicity

UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS, after a time offset4.

The time offset4 configured by the network indicating a time, after which the UE starts PDCCH monitoring via starting the new timer.
FFS: Definition of time offset4

Agreement

For the X = [2, 3] candidate values for the UE capability report on the minimum time gap for each SCS, consider {0.25, 0.5, 1, 2, 3, 6, 10, 20, 30, 40}ms

Note: Other values are not precluded
Only for reported value of [20ms,] 30ms and 40ms (if supported), the reported values assume SSB periodicity of 20ms and ensures SSB(s) before PDCCH reception and during time gap

FFS: translation of minimum time gap for different SSB periodicities including different candidates for different SSB periodicities

FFS whether the same set of candidates are used for different SCSs
FFS whether different values are selected for OOK-based WUR and OFDM-based WUR
FFS whether/how to consider the case of CA
FFS: candidate values that can be indicated by UAI

R1-2501587 Final summary on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

RAN1#120-bis

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-241824 for detailed scope of the WI. Additional RAN guidance on Rel-19 LP-WUS/WUR can be found in RP-243266.

[120bis-R19-LP_WUS] – Xin (vivo)

Email discussion on Rel-19 LP-WUS/WUR

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2501813 Updated RRC parameters list for Rel-19 LP-WUS/WUR vivo

R1-2503137 Summary of discussion on RRC parameters for Rel-19 LP-WUS/WUR vivo (WI rapporteur)

R1-2503100 Summary of RAN1 agreements on LP-WUS/WUR for NR Rapporteur (vivo)

9.6.1 LP-WUS and LP-SS design

R1-2501710 Discussion on LP-WUS and LP-SS Design FUTUREWEI

R1-2501737 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2501767 Discussion on LP-WUS design ZTE Corporation, Sanechips

R1-2501814 Remaining issues on LP-WUS and LP-SS design vivo

R1-2501845 Discussion on LP-WUS and LP-SS Design TCL

R1-2501875 Discussion on LP-WUS and LP-SS design Spreadtrum, UNISOC

R1-2501999 Design of LP-WUS and LP-SS CATT

R1-2503000 LP-WUS and LP-SS design Nokia (rev of R1-2502007)

R1-2502075 Discussion on LP-WUS and LP-SS design NEC

R1-2502167 Discussion on LP-WUS and LP-SS design CMCC

R1-2502237 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2502257 Signal design for LP-WUS and LP-SS OPPO

R1-2502302 Discussion on LP-WUS and LP-SS design InterDigital, Inc.

R1-2502322 LP-WUS and LP-SS design Sony

R1-2502375 Discussion on LP-WUS and LP-SS design Samsung

R1-2502448 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2502481 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2502580 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2502615 LP-WUS and LP-SS design Apple

R1-2502675 Discussion on LP-WUS and LP-SS design Sharp

R1-2502694 Discussion on LP-WUS and LP-SS design HONOR

R1-2502711 LP-WUS and LP-SS design MediaTek Inc.

R1-2502773 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2502805 LP-WUS and LP-SS design Ericsson

R1-2502846 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2502880 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2502908 Discussion on LP-WUS and LP-SS design Lenovo

R1-2503014 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Monday session

Agreement

From specification design perspective, for both RRC idle/inactive and RRC connected mode, support up to 5 information bits and up to 32 codepoints for a LP-WUS.

Agreement

Support maximum length for a LP-WUS (actual OFDM symbols used) which is larger than one slot.

· Non-consecutive OFDM symbols at least across multiple slots can be used for a LP-WUS transmission

Agreement

For RRC connected mode, maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell,

· support maximum 16 candidates overlaid sequences for M=1

· support maximum 8 candidates overlaid sequences for M=2

· support maximum 4 candidates overlaid sequences for M=4 (agreed in RAN1#119)

o FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.

· FFS: Whether or not the candidate set of overlaid sequences change across OOK ON chips

Agreement

For M=1, the overlaid OFDM sequence length , X is the number of RBs of LP-WUS/LP-SS bandwidth (blanked guard RBs are not included).

· The agreement overrides previous WA.

R1-2503015 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

R1-2503082 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Tuesday session

Agreement

Regarding whether to support additional sync signal to LP-SS, support the following for LP-WUS with M=1, M=2:

· Option 1A: No additional sync signal, LP-SS periodicity =320ms.

o Additionally support LP-SS periodicity of 160ms.

R1-2503083 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday session

Working Assumption

At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 (max 2 for each M value).

· Different roots can be picked for different M values.

Agreement

For > 2 information bits with RM coding, support the following alternative for rate matching after RM coding, when code block (coded bits) length after rate matching < 32

· Alt 1: Rate matching after RM coding is applied, as section 5.4.3 in TS 38.212.

Agreement

For the length L of LP-SS binary sequence, supports

· M=1, L= {6,8}

· M=2, L= {12,16}

· M=4, L= {16,32}

Note: For each value of M, UE supports both L values – no UE capability.

Note: There is no consensus in RAN1 that SNR of -3dB can be fulfilled with the smaller value of L for each M. Definition of the proper requirements for different values of L is up to RAN4.

Agreement

For LP-SS with M=4, supports set1 (balanced).

R1-2503097 Summary #5 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Thursday session

Agreement

For the root(s) used for overlaid OFDM sequences, gNB can configure any value from 1 ~ (B_zc-1), where Bzc is given by the largest prime number such that , is the overlaid OFDM sequence length.

Agreement

For > 2 information bits with RM coding, support candidate code block (coded bits) length after rate matching within the below range:

· Alt 1a: code block (coded bits) length: [3,4]~[32,64]

o FFS whether all or a subset of lengths is selected.

o FFS whether same range applies to all M values

FFS: above lengths do not consider repetition (if supported) after rate matching

R1-2503098 Summary #6 of discussions on LP-WUS and LP-SS design Moderator (vivo)

From Friday session

Agreement

For WUS information carried by the overlaid OFDM sequence(s):

· Alt 1: Raw information bits are mapped to sequence(s).

o N raw information bits are divided into K segments from MSB to LSB, where K= ceil (N/log₂L), L is the number of candidate overlaid OFDM sequences for one OOK ON chip.

o In one OOK ON chip, a segment of information bits is mapped to one sequence sequentially, e.g., for a segment of 2 information bits, 00 is mapped to sequence #1, 01 is mapped to seq #2.

o In case N/log₂L is not an integer, Bit 0 as MSB is used for padding.

Agreement

For RRC idle/inactive, support Alt 2 for both Redcap and non-redcap UEs:

· Alt 2: LP-WUS/LP-SS frequency resource can be out of initial DL BWP where UE receives paging but within the same carrier.

o FFS whether to define the maximum frequency gap between LP-WUS/LP-SS and SSB.

Working Assumption

Support 1 & 2 information bits for LP-WUS. No additional restriction is introduced on the supported number of subgroups/codepoints by LP-WUS.

2 information bits: coding is done as described in the first row in the table in section 5.3.3.2 of 38.212 (scrambling is not applied).
1 information bit: repetition is done as described in the first row in the table in section 5.3.3.1 of 38.212 (scrambling is not applied).

Agreement

For the M value for LP-WUS and LP-SS, supports:

Alt2: The M values for LP-WUS and LP-SS can be configured to be same or different. M value for LP-WUS cannot be larger than that of LP-SS.

At least for M values larger than 1 (applies to both LP-WUS and LP-SS).
FFS: If M=1 is configured for either of LP-WUS or LP-SS, M=1 is configured for both.

R1-2503099 Final summary of discussions on LP-WUS and LP-SS design Moderator (vivo)

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2501711 Discussion on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2501768 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE Corporation, Sanechips

R1-2501815 Remaining issues on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2501846 Discussion on LP-WUS Operation in IDLE/INACTIVE state TCL

R1-2501876 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum, UNISOC

R1-2502000 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2502008 LP-WUS operation in IDLE/Inactive mode Nokia

R1-2502076 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2502168 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2502238 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2502258 Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2502303 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2502323 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2502376 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2502449 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2502482 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2502516 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2502581 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2502616 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2502676 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2502712 LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

R1-2502774 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2502806 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2502847 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2502879 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2502907 Discussion on LP-WUS operation in Idle/Inactive modes Lenovo

R1-2502618 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Monday session

Agreement

Confirm the following working assumption with modifications in red:

Working Assumption

~~If LP-WUS design support 32 subgroups within one MO,~~ do not support Option 3 for LO to PO mapping or Option B for MO configuration.

Agreement

Option A for MO configuration is supported.

Agreement

A LP-WUS MO can span across multiple slots.

FFS the limitation on the maximum length for an LP-WUS MO

Agreement

Only R = 1 is supported for Option A.

Conclusion

For the offset value(s) between an LO and a reference PO/PF, do not support the configuration of 3 offset values.

Agreement

The maximum number of POs per LO is 4, and the number of POs per LO can be 1, 2 or 4.

R1-2502619 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Tuesday session

Agreement

For Option 2, the maximum value of M (number of LP-WUS MOs per beam) in Option A for MO configuration is 4.

Agreement

For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of beams corresponding to LP-WUS, and M is the number of LP-WUS MOs for each beam.

The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second).

Note: Above does not change the previous agreement on association between LP-WUS and SSB beams.

Agreement

For OFDM-based LP-WUR, reuse the LP-SS based LP-RSRP/LP-RSRQ definition of OOK-based LP-WUR.

FFS: Whether OFDM receiver can measure LP-SS if overlaid OFDM sequence is not configured (M=1).

Agreement

For LP-SSS-RSRP/RSSI measurement performed by OFDM-based LP-WUR for the serving cell, SMTC window is not applicable.

- Send an LS to RAN4 to confirm the above agreement.

R1-2503087 Draft LS on the RRM measurement metrics for OFDM-based LP-WUR Moderator (Apple)

From Thursday session

Agreement

LS on the RRM measurement metrics for OFDM-based LP-WUR is endorsed with the addition Cc to RAN2. Final LS is approved in R1-2503103.

· Note: RAN1 understanding is existing metrics SS-RSRP and SS-RSRQ are reused for OFDM-based LP-WUR. No separate metrics (LP-SSS-RSRP and LP-SSS-RSRQ) will be introduced in the specifications.

R1-2502620 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Agreement

For Option 2, at least one codepoint corresponding to each of the subgroups in each PO is supported.

For codepoint corresponding to more than one subgroups:

Alt 2: One codepoint for each PO corresponding to all the subgroups in the PO

Agreement

For Option 2, a common codepoint per PO is always used and the maximum number of subgroups supported per PO is

· 7 for the case where 4 POs are mapped to one LO

· 15 for the case where 2 POs are mapped to one LO

R1-2502621 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Thursday session

Agreement

Regarding whether there is any restriction on mapping multiple POs to one LO, no additional constraint for mapping multiple POs to one LO.

Agreement

UE determines whether a symbol is available for LP-WUS based on:

Alt 1: Time-domain pattern configured by the gNB

Alt 1A: Periodic time-domain pattern

E.g. (1) 1-slot periodicity, the pattern indicates the available symbols in each slot; (2) multi-slot or frame-level periodicity with a bitmap indication; (3) Search space set-like pattern; (4) multi-level time-domain patterns; (5) reuse the mechanism of rate matching pattern

Alt 1B: Per-MO pattern, applicable for all MOs

Alt 2: Information from existing configurations available for idle/inactive UEs such as [SSB, CORESET/Type-0 CSS, TDD DL/UL configuration, etc].
Alt 3: Combination of Alt 1 and Alt 2
Alt 4: NW ensures LP-WUS configuration without collision with existing signal(s).

Agreement

For the determination of starting time locations of LP-WUS MOs and LP-WUS transmissions in a LO,

A reference point is the start of a reference frame determined by the frame-level offset from the start of the first PF of the PF(s) associated with the LO.
The starting time location of the first LP-WUS MO in a LO is indicated by an offset w.r.t. the reference point.

FFS slot-level or symbol-level offset

The starting time locations of the subsequent LP-WUS MOs in a LO are determined based one of the following alternatives:

Alt 1: An offset is indicated for each of the subsequent LP-WUS MOs.

FFS slot-level or symbol-level offset

Alt 2: The start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.

FFS additional configuration to control the subsequent MO locations, e.g.,

Alt 2A: configuration of a single gap between the end of the previous MO (or a set of previous MOs) and the start of the next MO.
Alt 2B: configuration of candidate starting locations for MOs, similar to search space configuration.

FFS restriction on MO locations, e.g. only on DL slots.
FFS minimum gap is needed between two MOs to ensure LR processing time.

R1-2502622 Summary #5 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

From Friday session

Agreement

Terminology definition

Nominal MO duration: this includes both the available and unavailable symbols
Actual LP-WUS duration: the actual number of OFDM symbols used for LP-WUS transmission as assumed by the UE

Nominal MO duration and actual LP-WUS duration, if defined, are determined using one of the following alternatives:

Alt A: Nominal MO duration is configured. (e.g. in unit of slots)

Actual LP-WUS duration is the number of available symbols within the MO.
Actual LP-WUS duration can vary from one MO to another MO.

Alt B: Actual LP-WUS duration is configured. (e.g. in unit of OFDM symbols, or M and L values)

From the start of a MO, MO extends until the number of available OFDM symbols reaches the configured actual LP-WUS duration.

FFS: Additional termination condition such as time window.

Alt C: Both nominal MO duration and actual LP-WUS duration are configured.

If the number of available OFDM symbols within the nominal MO duration is less than the actual LP-WUS duration, the MO is considered as invalid (no LP-WUS monitoring in this MO) and dropped/deferred.

FFS UE behavior if there is no valid MO for the beam(s) that the UE monitors.

Note: the number of available OFDM symbols within a nominal MO duration can be different for different MOs.

Alt D: Nominal MO duration is configured. The actual LP-WUS duration is determined based on the same pattern for the available symbols for all the MOs (e.g. by using a per-MO pattern), which is the same for all the MOs.

Agreement

On how to handle the UE capability report on the wake-up delay for SSB periodicities other than 20ms, consider the following alternatives for possible down-selection in RAN1#121.

· Alt 1: Do not report for SSB periodicities other than 20ms.

o Note: LP-WUS is not supported for SSB periodicities larger than 20ms.

· Alt 2: For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):

SSB periodicity (ms)	Wake-up delay (ms) UE capability 1	Wake-up delay (ms) UE capability 2	Wake-up delay (ms) UE capability 3
[5]	[x]	[x]	[x]
[10]	[x]	[x]	[x]
20	[70]	[500]	[900]
[40]	[x]	[x]	[x]
[80]	[x]	[x]	[x]
[160]	[x]	[x]	[x]

Alt 3: It is up to RAN4.

Agreement

Each LP-SS transmission for each beam always occupies consecutive OFDM symbols.

Final summary in R1-2503147.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2501769 Discussion on LP-WUS operation in CONNECTED mode ZTE Corporation, Sanechips

R1-2501816 Remaining issues on LP-WUS operation in CONNECTED modes vivo

R1-2501877 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum, UNISOC

R1-2502001 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2502009 LP-WUS operation in CONNECTED mode Nokia

R1-2502060 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2502077 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2502169 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2502239 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2502259 Further consideration on LP-WUS operation in connected mode OPPO

R1-2502304 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2502324 LP-WUS operation in CONNECTED mode Sony

R1-2502377 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2502450 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2502483 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2502517 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2502576 Discussion on LP-WUS procedures in Connected mode TCL

R1-2502617 LP-WUS operation in CONNECTED modes Apple

R1-2502677 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2502713 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2502775 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2502807 LP-WUS operation in CONNECTED mode Ericsson

R1-2502848 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2502997 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Monday session

Agreement

· For the case when UE is configured with CA without dual DRX groups in RRC CONNECTED mode, LP-WUS can be configured only on PCell.

· For the case when UE is configured with NR-DC with CA without dual DRX groups or without CA in RRC CONNECTED mode, LP-WUS can be configured only on PCell/PSCell per cell-group.

R1-2503055 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Tuesday session

Conclusion

From RAN1 perspective, when LP-WUS monitoring Option 1-2 is enabled for RRC CONNECTED mode, it is supported that SR, PRACH and CG-PUSCH triggers PDCCH monitoring according to the legacy UE behaviour.

Conclusion

For the case when UE is configured with CA with dual DRX groups in RRC CONNECTED mode, at least for LP-WUS procedure Option 1-1, there is no consensus in RAN1 which of the following options to support for this case in Rel-19.

Alt1

Basic capability

LP-WUS can be configured only on PCell
LP-WUS indication is applicable to all serving cells of all DRX groups.

Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation

Advanced capability

LP-WUS can be configured on PCell for primary DRX group and an activated SCell for secondary DRX group
LP-WUS indication is applicable to all serving cells in the DRX group where LP-WUS is monitored

Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation

This capability has prerequisite of the above basic capability

Alt2

LP-WUS can be configured on PCell for primary DRX group and/or an activated SCell for secondary DRX group
LP-WUS indication is applicable to all serving cells in the DRX group where LP-WUS is monitored

Note: There is no impact to PDCCH monitoring behaviour related to SCell dormancy/activation/deactivation

This capability has candidate values for the LP-WUS configuration with {primary DRX group, secondary DRX, both}

Agreement

Update previous agreement in red:

Agreement

For LP-WUS MOs in connected mode for Option 1-1, support Approach 1:

· LP-WUS MOs, including periodicity and time offset1, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).

· Time offset2 indicates a time prior to a slot where the drx-onDurationTimer would start

o UE monitors the first Z LP-WUS MO(s) at or after Time offset2.

§ ~~FFS: How to determine the value of~~ Z is RRC configured

o Time offset2 is RRC configured

UE is not required to monitor LP-WUS during the X [slots/symbols] prior to the beginning of a slot where the UE would start the drx-onDurationTimer. ~~FFS: How~~ X is ~~determined~~ given based on the minimum time gap reported by UE capability.

R1-2503088 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

Update previous agreement in red:

Agreement

For LP-WUS MOs in connected mode for Option 1-2, support Approach 1:

· LP-WUS MOs, including a periodicity and a time offset3, are configured independently from the C-DRX periodicity/offset by new RRC parameter(s).

o ~~FFS one or multiple MOs per periodicity~~

o UE is configured with a number of MOs for the periodicity by RRC.

· UE monitors LP-WUS in the LP-WUS MOs and, if triggered to wake up, starts a new timer for PDCCH monitoring triggered by LP-WUS

o ~~FFS: Definition of time offset4~~

o Alt1:

§ ~~The~~A time offset4 configured by the network indicating a time from the first LP-WUS MO per periodicity, after which the UE starts PDCCH monitoring via starting the new timer.

§ The time gap from the last LP-WUS MO per periodicity and the start of new timer is not smaller than the minimum time gap given based on UE capability.

Agreement

For the UE capability report on the minimum time gap is between the end of the last symbol of LP-WUS and the time where MR starts PDCCH monitoring regardless of SCS, support X=3 candidate values corresponding to {V1=[3,5,6], V2=[10,13,20], V3=[33,42]}ms where V1<V2<V3.

· FFS: Whether to support different set of values for different receiver types.

Conclusion

There is no consensus in RAN1 on whether to introduce any enhancements of PDCCH skipping indication for the interaction with LP-WUS in RRC connected mode in Rel-19.

Agreement

For RRC CONNECTED mode when LP-WUS is configured with Cell DTX, during Cell DTX inactive time, the UE is not expected to monitor LP-WUS both for Option 1-1 and 1-2.

R1-2503102 FL summary #4 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Thursday session

Agreement

The case where a UE does NOT supports Rel-17 unified TCI framework but supports LP-WUS is supported in Rel-19. For the TCI state of LP-WUS in RRC CONNECTED mode, select one of the following in RAN1#121 for this case:

Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS.
Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them.

The case where a UE supports Rel-17 unified TCI framework and supports LP-WUS is supported in Rel-19. For the TCI state of LP-WUS in RRC CONNECTED mode,

When Rel-17 unified TCI framework is configured, LP-WUS follows the activated/indicated TCI-state by MAC-CE/DCI, same as other DL channels/signals (no change to DCI format).
When Rel-17 unified TCI framework is NOT configured, select one of the following in RAN1#121 for this case:

Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS.
Alt2: RRC configures K TCI states for LP-WUS and new MAC-CE for TCI activation activates one of them.

Same alternative to be chosen for both cases.

R1-2503120 FL summary #5 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

From Friday session

Agreement

Update previous agreement in red:

Agreement

For LP-WUS monitoring in RRC CONNECTED mode, SSB and/or CSI-RS can be the QCL source of LP-WUS QCL type(s) is {~~Type A or~~ Type C ~~– for down-selection}~~ and Type D, when applicable.

R1-2503121 Final summary on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

RAN1#121

9.6 Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Please refer to RP-241824 for detailed scope of the WI. Additional RAN guidance on Rel-19 LP-WUS/WUR can be found in RP-243266.

[121-R19-LP_WUS] Email discussion on Rel-19 LP-WUS/WUR – Xin (vivo)

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2503368 Updated RRC parameters for Rel-19 LP-WUS/WUR vivo

9.6.1 LP-WUS and LP-SS design

R1-2503228 Remaining Issues on LP-WUS and LP-SS Design FUTUREWEI

R1-2503290 Signal Design of LP-WUS and LP-SS Huawei, HiSilicon

R1-2503318 Discussion on LP-WUS design ZTE Corporation, Sanechips

R1-2503369 Remaining issues on LP-WUS and LP-SS design vivo

R1-2503522 Discussion on LP-WUS and LP-SS design Spreadtrum, UNISOC

R1-2503573 Discussion on LP-WUS and LP-SS design Samsung

R1-2503631 Discussion on LP-WUS and LP-SS Design TCL

R1-2503694 LP-WUS and LP-SS design Nokia

R1-2503724 Discussion on LP-WUS and LP-SS Design EURECOM

R1-2503800 Design of LP-WUS and LP-SS CATT

R1-2503838 Discussion on LP-WUS and LP-SS design CMCC

R1-2503889 Discussion on LP-WUS and LP-SS design Xiaomi

R1-2503938 Discussion on LP-WUS and LP-SS design NEC

R1-2503964 Discussion on LP-WUS and LP-SS design InterDigital, Inc.

R1-2504018 LP-WUS and LP-SS design Ericsson

R1-2504066 LP-WUS and LP-SS design Sony

R1-2504102 Discussion on LP-WUS and LP-SS design HONOR

R1-2504187 Signal design for LP-WUS and LP-SS OPPO

R1-2504237 Discussion on the LP-WUS and LP-SS design Panasonic

R1-2504250 Discussion on LP-WUS and LP-SS design LG Electronics

R1-2504265 LP-WUS and LP-SS design MediaTek Inc.

R1-2504328 LP-WUS and LP-SS design Apple

R1-2504401 LP-WUS and LP-SS design Qualcomm Incorporated

R1-2504437 Discussion on LP-WUS and LP-SS design Sharp

R1-2504508 Discussion on LP-WUS and LP-SS design NTT DOCOMO, INC.

R1-2504575 On LP-WUS and LP-SS design Nordic Semiconductor ASA

R1-2504723 Summary #1 of discussions on LP-WUS and LP-SS design Moderator (vivo)

Agreement

For LP-WUS/LP-SS frequency resource configuration, the starting PRB index with reference to carrier boundary determined by offsetToCarrier corresponding to SCS of the active BWP or legacy DL initial BWP is configured by gNB, with range of 0~263. Starting PRB index configured for LP-WUS is same as that of LP-SS.

Agreement

Confirm the following working assumption with revision in red

Working Assumption

At least for FR1, support maximum 2 roots to be used for overlaid OFDM sequences for M=1/2/4 (max 2 for each M value).

Different roots can be picked for different M values.

Above applies for LP-WUS

Agreement

Update the agreements as below:

Agreement

For idle mode, regarding the maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell:

- support maximum 16 candidates overlaid sequences for M=1

- support maximum 8 candidates overlaid sequences for M=2

- For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value.

o ~~FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.~~

Agreement

For RRC connected mode, maximum number of candidates overlaid sequences to carry LP-WUS information per OOK ON chip for one cell,

- support maximum 16 candidates overlaid sequences for M=1

- support maximum 8 candidates overlaid sequences for M=2

- support maximum 4 candidates overlaid sequences for M=4 (agreed in RAN1#119)

- For candidate overlaid sequences across all OOK ON chips of LP-WUS, the number of roots (in specification) is up to [FFS: X], FFS whether the number of roots can be different for different M value.

o ~~FFS: The number of overlaid sequences applicable for a UE is no more than 2 per OOK ON chip.~~

- ~~FFS: Whether or not the candidate set of overlaid sequences change across OOK ON chips~~

Note: The WUS information carried by overlaid OFDM sequence is based on codepoint i.e. raw information bit

R1-2504724 Summary #2 of discussions on LP-WUS and LP-SS design Moderator (vivo)

Agreement

From RAN1 perspective, there is no restriction on the maximum frequency bandwidth covering both LP-WUS/LP-SS and SSB.

- It is up to RAN4 to introduce any restriction depending on their discussions

- Above applies for IDLE and INACTIVE mode UEs

Agreement

For code block (coded bits) length L after rate matching as defined in 38.212 section 7.4.2.1, support

- For 1 information bit, L is in 1~32

- For 2 information bits, L is in 2~32

- For 3 information bits, L is in 3~32

- For 4 information bits, L is in 5~32

- For 5 information bits, L is in 6~32

- For M=4, the code block (coded bits) length L is even number.

- Further restriction on the L value within above range is not precluded.

- Do not support repetition after rate matching

Agreement

For both FR1 and FR2, when M value for LP-WUS is 1, the M values for LP-SS can be configured as 1, 2, or 4.

Agreement

Confirm the following working assumption

Working Assumption

Regarding the LP-WUS information to trigger PDCCH monitoring of RRC connected UEs:

- Codepoint based

o The maximum number of codepoints checked per MO by a UE is up to 8

Depending on UE capability, a UE may support less than 8

R1-2504831 Summary #3 of discussions on LP-WUS and LP-SS design Moderator (vivo)

Agreement

For mapping between a sequence index and root value () & CS value ().

where cyclic shift value is determined by

R1-2504832 Summary #4 of discussions on LP-WUS and LP-SS design Moderator (vivo)

Agreement

Support LP-WUS with M=4 for 30kHz SCS without separate UE capability.

- No additional sync signal for this case, LP-SS periodicity =320ms and 160ms

Agreement

For the overlaid OFDM sequence for LP-SS in one cell, single root is used and gNB can configure any value from 1 ~ (Bzc -1), where Bzc is given by the largest prime number such that , and is the overlaid OFDM sequence length.

- cyclic shift value.

- Note: Different roots can be used to differentiate overlaid OFDM sequences for LP-SS from different cells

Agreement

For LP-WUS in FR2, support M=1 for 120kHz in both RRC idle/inactive and RRC connected, and M=1, 2 for SCS=60kHz in RRC connected only.

Agreement

For LP-WUS in FR2, the number of roots and number of sequences are

- Max 2 roots and max 4 sequences for M =1 for SCS 60kHz

- Max 2 roots and max 2 sequences for M=2 for SCS 60kHz

- Max 2 roots and max 2 sequences for M=1 for SCS 120kHz

Agreement

Confirm the following working assumption

Working Assumption

Support 1 & 2 information bits for LP-WUS. No additional restriction is introduced on the supported number of subgroups/codepoints by LP-WUS.

- 2 information bits: coding is done as described in the first row in the table in section 5.3.3.2 of 38.212 (scrambling is not applied)

- 1 information bit: repetition is done as described in the first row in the table in section 5.3.3.1 of 38.212 (scrambling is not applied)

Agreement

For LP-WUS overlaid OFDM sequence configuration in a cell,

- gNB configures number of sequences Nseq, and one or two root values.

o Alt1: Nseq is 2^n, where the value range of n is 0~4, 0~3, 0~2 for M=1, 2, 4, respectively.

§ No separate UE capability for different n values.

o Nroot=2, when Nseq=16,8,4 for M=1,2,4, where Nroot is the number of root values.

§ Nroot=1 or 2 when Nseq is other value

- The number of CS Ncs is derived by Nseq/Nroot

R1-2504907 Reply LS on LP-WUS UE RF RAN1, vivo

LS on LP-WUS UE RF to RAN4 is endorsed in R1-2504943.

9.6.2 LP-WUS operation in IDLE/INACTIVE modes

R1-2503229 Remaining Issues on LP-WUS Operation in IDLE/INACTIVE Modes FUTUREWEI

R1-2503291 Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode Huawei, HiSilicon

R1-2503319 Discussion on LP-WUS operation in IDLE/INACTIVE mode ZTE Corporation, Sanechips

R1-2503370 Remaining issues on LP-WUS operation in IDLE/INACTIVE modes vivo

R1-2503523 Discussion on LP-WUS operation in IDLE/INACTIVE modes Spreadtrum, UNISOC

R1-2503574 Discussion on LP-WUS operation in IDLE/INACTIVE modes Samsung

R1-2503643 Discussion on LP-WUS Operation in IDLE/INACTIVE modes TCL

R1-2503695 LP-WUS operation in IDLE/Inactive mode Nokia

R1-2503801 System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes CATT

R1-2503839 Discussion on LP-WUS operation in IDLE/INACTIVE modes CMCC

R1-2503890 Discussion on LP-WUS operation in Idle/Inactive modes Xiaomi

R1-2503939 Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode NEC

R1-2503965 Discussion on LP-WUS operation in IDLE/INACTIVE modes InterDigital, Inc.

R1-2504019 LP-WUS operation in IDLE and INACTIVE modes Ericsson

R1-2504067 LP-WUS operation in IDLE / INACTIVE modes Sony

R1-2504144 Discussion on LP-WUS operation in IDLE/INACTIVE modes ETRI

R1-2504188 Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes OPPO

R1-2504238 Discussion on LP-WUS operation in IDLE/INACTIVE modes Panasonic

R1-2504251 Discussion on LP-WUS operation in IDLE/INACTIVE modes LG Electronics

R1-2504266 LP-WUS operation in IDLE/INACTIVE modes MediaTek Inc.

R1-2504329 LP-WUS operation in IDLE/INACTIVE modes Apple

R1-2504335 Summary #5 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

R1-2504402 LP-WUR operation in idle and inactive modes Qualcomm Incorporated

R1-2504438 Discussion on LP-WUS operation in IDLE/INACTIVE modes Sharp

R1-2504509 Discussion on LP-WUS operation in IDLE/INACTIVE modes NTT DOCOMO, INC.

R1-2504574 On LP-WUS operation in IDLE/Inactive Nordic Semiconductor ASA

R1-2504331 Summary #1 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Agreement

It can be configured by the gNB in the LP-WUS/LP-SS configuration on whether LP-WUS/LP-SS transmission is present or not for each beam of the actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1.

· For the LP-WUS MO and LP-SS occasion determination,

o Alt 1: S is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1, and LP-WUS MOs and LP-SS occasions are determined assuming S beams. gNB transmits LP-WUS/LP-SS in a subset of the S beams according to the LP-WUS/LP-SS configuration.

§ FFS: Additional details on Alt 1 to be finalized in RAN1#121

· If not configured, UE assumes LP-WUS/LP-SS transmission is present for all the actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1

Agreement

Each LP-SS transmission for each beam is contained within one slot.

R1-2504332 Summary #2 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Agreement

For LP-SS, the LP-SS occasions are indexed sequentially in time, and the n-th LP-SS occasion is associated with the beam of the n-th transmitted SSB, n = 1, 2, …, N, where N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1.

The RAN1#120bis agreement is updated as follows:

For LP-WUS, the N * M LP-WUS MOs in an LO are indexed sequentially in time, from 1 to N*M, where N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 ~~the number of beams corresponding to LP-WUS~~, and M is the number of LP-WUS MOs for each beam.

The (n*M+m+1)-th LP-WUS MO corresponds to the (n+1)-th beam, which is associated with the beam of the (n+1)-th transmitted SSB, where m=0,1,…,M-1, n=0,1,2,…,N-1. (multiple MOs first, beam second)

Agreement

For UE capability report on the wake-up delay, the UE reports one of the following 3 capabilities (the values in one of the columns):

SSB periodicity (ms)	Wake-up delay (ms) UE capability 1	Wake-up delay (ms) UE capability 2	Wake-up delay (ms) UE capability 3
5/10/20	[70]	[500]	[900]
40	[x]	[x]	[x]
80	[x]	[x]	[x]
160	[x]	[x]	[x]

Agreement

If the number of POs associated with a LO is less than Ns (the number of POs per PF), to determine the LP-WUS MOs for the multiple LOs with the same reference PF:

· Alt 1: additional frame-level offset(s) are configured.

o Common slot-level or symbol level offsets are shared across all LOs

R1-2504333 Summary #3 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Agreement

For the configuration on whether LP-WUS/LP-SS transmission is present or not for each beam of the actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1:

· use bitmap, with one bit corresponding to each of the SSB beams (similar to existing indication for ssb-PositionsInBurst)

Agreement

For PO-to-LO association and codepoint determination, assume is the number of POs associated with a LO, is the number of subgroups per PO for LP-WUS, and is the subgroup ID of a UE ().

The PO index within the LO is defined as

The reference PF for the LO of a PO is provided by (SFN for PF) – floor(i_PO/N_S) * T/N, which is the first PF of the PF(s) associated with the LO.
For the codepoints,

If >1,

The number of information bits in LP-WUS is .
Alt 2: (the codepoints for each PO are consecutive)

The codepoint for subgroup in PO is .
The codepoint for all the subgroups in PO is (.

If 1, the number of information bits in LP-WUS is , and the codepoint for PO is .

Here UE_ID (for LP-WUS), N, N_S, and T are defined in TS 38.304

R1-2504334 Summary #4 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Agreement

For UE to determine whether a symbol is available for LP-WUS, at least the following is supported:

· A unit-level bitmap with a periodicity 10, 20, or 40 units and a 14-bit or 28-bit symbol-level bitmap that covers 1 or 2 slots can be configured, where each unit is 1 or 2 slots for 14-bit or 28-bit symbol-level bitmap, respectively, with a maximum periodicity of 40ms.

o ‘1’ in unit-level bitmap means the symbol level bitmap is applied to determine which symbols are unavailable in the unit for LP-WUS (‘0’ means unavailable).

o ‘0’ in unit-level bitmap means: all the symbols in the unit are unavailable for LP-WUS

· If the slot-level bitmap is not configured, UE assumes all 1’s for the bitmap.

· If the symbol-level bitmap is not configured, UE assumes all 1’s for the bitmap.

Agreement

For the handling of SSB for IDLE mode, the SSB symbols are considered as unavailable for LP-WUS, if SSB and LP-WUS overlap in frequency domain

R1-2504335 Summary #5 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Agreement

Nominal MO duration (X1, in unit of OFDM symbols) and actual LP-WUS duration (X2, in unit of OFDM symbols) are configured. (Alt C)

· A LP-WUS MO spans the nominal MO duration (i.e., the LP-WUS MO duration is the same as the nominal MO duration.)

· If the number of available OFDM symbols within the nominal MO duration is no less than the actual LP-WUS duration, UE monitors LP-WUS on the first X2 available symbols within the LP-WUS MO.

· Otherwise, UE does not monitor LP-WUS in this MO (i.e., the MO is dropped).

· Note: Any symbols that are not defined as unavailable are available symbols for LP-WUS.

Agreement

The starting time location of the first LP-WUS MO in a LO is configured by an offset w.r.t. the reference point, where the offset is a symbol-level offset

Agreement

If LP-SS is configured, the periodicity is configured with the candidate value set of {160ms, 320ms}.

· A time offset is configured for the first LP-SS occasion with reference to SFN0

o If the periodicity is 160ms, the candidate value set for the time offset is {0, 1, …, 159}ms.

o If the periodicity is 320ms, the candidate value set for the time offset is {0, 1, …, 319}ms.

Agreement

The number of MOs per beam per LO is configured by gNB, with candidate value set of {1, 2, 3, 4}.

Agreement

The candidate value set for the frame-level offset(s) is {8, 9, …, 200} in unit of frames.

- The minimum value can be modified depending on relevant RAN4 outcome

R1-2504335 Summary #5 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

R1-2504891 Summary #6 on LP-WUS operation in IDLE/INACTIVE mode Moderator (Apple)

Agreement

For UE to determine the LP-SS occasions,

· One or two start symbol locations within a slot are configured.

o Candidate value range for each start symbol location: {0, 1, …, 10}.

o If one value is configured, there is one LP-SS occasion in a slot.

o If two values are configured, there are two LP-SS occasions in a slot.

· Starting from the slot for the first LP-SS occasion (determined from the periodicity/offset configuration for LP-SS), LP-SS occasions are present in this slot and the next (ceil(X/Y)-1) DL slots, where X is the number of SSBs determined according to ssb-PositionsInBurst in SIB1, and Y is the number of LP-SS occasions in a slot.

o UE expects the slot for the first LP-SS occasion is a DL slot.

o Note: a slot is a DL slot if all the symbols in the slot are indicated as DL symbols in tdd-UL-DL-ConfigurationCommon.

· Note: UE follows the configured resources for LP-SS processing.

Agreement

In one LO, the start time location of a subsequent LP-WUS MO is determined implicitly at least based on the previous LP-WUS MO.

· No additional RRC configuration is provided.

· FFS whether/how to ensure a gap between two LP-WUS MOs

Agreement

The OFDM symbols configured for Type-0 CSS are considered as unavailable for LP-WUS if CORESET#0 and LP-WUS overlap in frequency domain.

Agreement

The UL symbols/slots configured in tdd-UL-DL-ConfigurationCommon are considered as unavailable for LP-WUS.

Agreement

If LP-SS overlap (including partial overlap) in time domain with the available symbols that may be used for LP-WUS transmission in a LP-WUS MO, UE does not monitor LP-WUS in this MO (i.e., the MO is dropped).

Agreement

For the EPRE ratio between LP-WUS/LP-SS and SSB (i.e. LP-WUS/LP-SS EPRE divided by SSB EPRE), separate configurations are provided for LP-WUS and LP-SS.

· The candidate value set for the EPRE ratio is {-3dB, 0 dB, 3 dB, 6 dB}.

· If M=1 for both LP-WUS and LP-SS, or M>1 for both LP-WUS and LP-SS, the difference between the two EPRE ratios shall be no larger than 3 dB.

· If M=1 for LP-WUS and M>1 for LP-SS, the ERPE ratio for LP-SS minus the EPRE ratio for LP-WUS should be within the range of -6 dB to 0 dB.

Note: EPRE refers to EPRE in one OFDM symbol with non-zero power (from baseband perspective) LP-WUS/LP-SS transmission.

9.6.33 LP-WUS operation in CONNECTED modes

R1-2503292 Procedures and functionalities of LP-WUS in CONNECTED mode Huawei, HiSilicon

R1-2503320 Discussion on LP-WUS operation in CONNECTED mode ZTE Corporation, Sanechips

R1-2503371 Remaining issues on LP-WUS operation in CONNECTED modes vivo

R1-2503524 Discussion on LP-WUS operation in CONNECTED modes Spreadtrum, UNISOC

R1-2503575 Discussion on LP-WUS operation in CONNECTED modes Samsung

R1-2503696 LP-WUS operation in CONNECTED mode Nokia

R1-2503748 Discussion on LP-WUS operation in CONNECTED mode Panasonic

R1-2503802 System design and procedure of LP-WUS operation for UE in CONNECTED Modes CATT

R1-2503840 Discussion on LP-WUS operation in CONNECTED mode CMCC

R1-2503891 Discussion on LP-WUS operation in Connected mode Xiaomi

R1-2503940 Discussion on LP-WUS operation in RRC CONNECTED mode NEC

R1-2503966 Discussion on RRC CONNECTED mode LP-WUS monitoring InterDigital, Inc.

R1-2504020 LP-WUS operation in CONNECTED mode Ericsson

R1-2504145 Discussion on LP-WUS operation in CONNECTED modes ETRI

R1-2504189 Further consideration on LP-WUS operation in connected mode OPPO

R1-2504252 Discussion on LP-WUS operation in CONNECTED modes LG Electronics

R1-2504267 LP-WUS operation in CONNECTED modes MediaTek Inc.

R1-2504330 LP-WUS operation in CONNECTED modes Apple

R1-2504403 LP-WUR operation in connected mode Qualcomm Incorporated

R1-2504439 Discussion on LP-WUS operation in CONNECTED modes Sharp

R1-2504510 Discussion on LP-WUS operation in CONNECTED mode NTT DOCOMO, INC.

R1-2504588 Discussion on LP-WUS procedures in Connected mode TCL

R1-2504713 FL summary #1 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

Agreement

For LP-WUS MOs in connected mode for Option 1-1/1-2, the time offset1/3 in previous agreement are configured relative to the start of SFN0 where the offset is a symbol-level offset

Agreement

As the initial reply to RAN2 LS in R1-2503616, RAN1 confirms that at least the collision with Active Time, measurement gap, and RAR window monitoring for BFR can be considered for the cases/scenarios on when the UE is not able to monitor LP-WUS.

R1-2504805 FL summary #2 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

Agreement

For LP-WUS monitoring in RRC CONNECTED mode, when Rel-17 unified TCI framework is NOT configured or UE does NOT support Rel-17 unified TCI framework

- Alt1: RRC provides the CORESET ID that UE shall derive the active TCI state for LP-WUS

R1-2504833 FL summary #3 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

Conclusion

There is no consensus in RAN1 whether to specify UE autonomous fallback to PDCCH monitoring when UE monitors LP-WUS in RRC CONNECTED mode

Agreement

As the reply to RAN2 LS in R1-2503616, RAN1 assumes that UE is not able to operate LR and MR simultaneously in Rel-19. RAN1 understanding is that the terminology of LR and MR operations are for discussion purpose and will not be specified

- LR operation is the UE operation for LP-WUS monitoring

- MR operation is the UE operation for all other NR signals/channels transmissions/receptions in connected mode

Conclusion

From RAN1 perspective, for the case of potential collision (if any) in Option 1-2, when the UE is not able to monitor all the LP-WUS MO(s) in a LP-WUS periodicity,

- It is up to RAN2 to further discuss and finalize the specification support, if any.

Agreement

For the UE capability report on the minimum time gap between the end of the last symbol of LP-WUS and the time where MR starts PDCCH monitoring regardless of SCS, the same candidate values {V1, V2, V3} are supported for different receiver types

- V1=5ms

- V2=13ms

- V3=37ms

Agreement

For the UAI of preferred time offset for LP-WUS monitoring in RRC connected mode,

- The candidate values are same as those for the UE capability of minimum time gap, i.e., {V1=5, V2=13, V3=37}ms

- The reported UAI value is equal to or longer than the minimum time gap reported by UE capability for a UE

Note: There is no change to the RAN1 agreed definition for UAI

R1-2504886 FL summary #4 on LP-WUS operation in CONNECTED mode Moderator (NTT DOCOMO)

R1-2504887 Draft reply LS on LP-WUS in RRC_CONNECTED Moderator (NTT DOCOMO)

Final reply LS on LP-WUS in RRC_CONNECTED is endorsed in R1-2504888

Agreement

Nominal MO duration (X1, in unit of OFDM symbols) and actual LP-WUS duration (X2, in unit of OFDM symbols) are configured for LP-WUS in connected mode. (Alt C)

A LP-WUS MO spans the nominal MO duration (i.e., the LP-WUS MO duration is the same as the nominal MO duration.)
If the number of available OFDM symbols within the nominal MO duration is no less than the actual LP-WUS duration, UE monitors LP-WUS on the first X2 available symbols within the LP-WUS MO.
Otherwise, UE does not monitor LP-WUS in this MO (i.e., the MO is dropped).
Note: Any symbols that are not defined as unavailable are available symbols for LP-WUS.
Further discuss possible introduction of UE capability to restrict configuration of LP-WUS MO and LP-WUS duration. For example,

o A LP-WUS spans a number of consecutive OFDM symbols according to the configured LP-WUS duration

o If there is at least one OFDM symbol unavailable for the LP-WUS MO within the OFDM symbols where the LP-WUS would span, the UE does not monitor the LP-WUS in the MO

Agreement

For UE to determine whether a symbol is available for LP-WUS in connected mode, at least the following is supported:

· A unit level bitmap with a periodicity 10, 20, or 40 units and a 14-bit or 28-bit symbol-level bitmap that covers 1 or 2 slots can be configured, where each unit is 1 or 2 slots for 14-bit or 28-bit symbol-level bitmap, respectively, with a maximum periodicity of 40ms.

o ‘1’ in unit-level bitmap means the symbol level bitmap is applied to determine which symbols are unavailable in the unit for LP-WUS (‘0’ means unavailable).

o ‘0’ in unit-level bitmap means: all the symbols in the unit are unavailable for LP-WUS

· If the slot-level bitmap is not configured, UE assumes all 1’s for the bitmap.

· If the symbol-level bitmap is not configured, UE assumes all 1’s for the bitmap.

Agreement

For the handling of at least PCell/PSCell SSB for connected mode, the SSB symbols are considered as unavailable for LP-WUS

Agreement

The UL symbols/slots configured in tdd-UL-DL-configurationCommon or tdd-UL-DL-ConfigurationDedicated are considered as unavailable for LP-WUS in connected mode